> On 2007.04.19 at 11:59:39 -0700, David Schwartz wrote: > > > This is not nearly as simple as you might think. Are 'foo.txt' > and 'Foo.txt' the same file? What about 'directory/file.txt' and > 'symlink/file.txt'? > > > > I don't see how you can do this without making assumptions about the > > semantics of the filesystem involved. These assumptions will sometimes > > I don't see why these assumptions cannot be done at compile time. > There exists few different filesystem semanctics:
The filesystem is not known at compile time. > Unix one, > DOS/Windows one, > VMS (versioned) one. These are *OS* semantics. Linux, for example, supports filesystems with Unix semantics, DOS (case-insensitive) semantics, and versioned filesystems. > OpenSSL already have sophisticated compile-time configuration system, > which handle quite a few semantic differences between these platforms. > So, it is possible to add this one. These are not platform differences but filesystem differences. If the filesystem is accessed using NFS, it might not even be a filesystem whose semantics exist natively on that platform. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED]
