[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Stefan Monnier
Subject: Re: loaddefs.el filenames as seen by `update-file-autoloads'
Date: Tue, 13 May 2003 10:00:54 -0400

>    From: "Stefan Monnier" <monnier+gnu/address@hidden>
>    Date: Mon, 12 May 2003 21:14:13 -0400
>    Under W32, the file-system preserves the capitalization, even though
>    it ignores it when searching for files.  I.e. you can't have both "Foo"
>    and "FOO", but after creating "Foo", an application can know whether
>    the file was created as "Foo" or "foo" or "FOO".
>    If `directory-files' *can* properly return ("ChangeLog" "README"
>    "configure"), rather than ("changelog" "readme" "configure") or
>    ("CHANGELOG" "README" "CONFIGURE"), without having to read the user's
>    mind (and without performance cost) then I think it should.
> ok, i see what you mean.  i see that `readdir' for vms (in sysdep.c)
> does no case translation, and stepping through that function a few times
> in the debugger shows the filename to be upcased from the beginning.  it
> looks like vms that i am using follows the last of the three models
> above.

In that case, it probably makes sense to keep all file names
upcased, indeed.

But that means that there is no way we can reliably use on Unix
a loaddefs.el generated on VMS.  So I think the thing we should
do is use something like `file-name-equal' rather than string=.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]