Re: loaddefs.el filenames as seen by `update-file-autoloads'

[Thien-Thi Nguyen <ttn@glug.org>]

   From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
   Date: Mon, 12 May 2003 19:05:14 -0400

   Any reason why it's upcased ?
   Is it just the tradition under VMS ?

i don't know about the internals of other programs under vms, but yes,
traditionally (Richard Levitte's work) emacs has upcased filenames.  i
suppose there may be code that relies on this behavior by now.  one
notable exception is the buffer name -- that is downcased.

   At least under Emacs, the tradition is rather to use lowercase for
   most file names, so it would make more sense to downcase (and most
   places where we want to ignore case, we downcase rather than upcase,
   your code below being a prime example).

ok.

   Also it would be better to do what W32 does: preserve capitalization.
   Is that possible ?

a directory listing from the command line shows filenames all uppercase,
so upcasing everything internally is indeed preserving capitalization.
(this possibility is the current reality.)  perhaps i misunderstand you.

   I'd rather use file-name-equal.

thanks for the tip -- will check it out.  i'm working from 21.2 release
at the moment, will move to 21.3 after "make bootstrap" (actually "mms
bootstrap") works.

   Admittedly, since loaddefs.el is still under CVS control and is hence
   shared between all kinds of systems, it might be better to just
   systematically downcase, independently from the system in use.

yes, this is one important factor that i didn't mention: future
harmonization of build process, including supporting "make bootstrap"
from fresh cvs checkout.

   Hold it.  What about the file name in the (autoload ...) form ?

the cvs loaddefs.el uses lowercase.  the change i proposed would
maintain that convention.  this is possible because under vms,
`expand-file-name' upcases (and practically everything filesystem
related passes through that function at some point -- sometimes
multiply!).

   Since the `autoload' might be used on case-sensitive systems, it
   needs to have the right capitalization (now there's an example where
   preserving capitalization in filenames (even if you ignore it) is
   beneficial).

well, unixoids are case-sensitive.  we sidestep the problem there by
adhering in practice to lowercase filenames that moreover are unique
amongst themselves w/o regard to case.  the proposed change is not for
all systems, but only those that are vms-like.

   > changing `load-name' instead of making the comparison case-insensitive
   > means loaddefs.el will have lowercased frags (under vms), a change that
   > is transparent to `expand-file-name'.  is this ok?  other ideas?

   I don't understand your references to expand-file-name.
   Could you lay out what you mean ?

here is an example under vms:

  (expand-file-name "foo.el") => "AXPA:[TTN.EMACS.EMACS212_3]FOO.EL"

because autoloading eventually triggers loading which eventually uses
`expand-file-name', we don't need to store "FOO.EL" in loaddefs.el to
actually access "FOO.EL" on disk; "foo.el" is sufficient (under vms).

thi