Mail Archives: cygwin/2001/02/27/14:10:00
I do like the new symlink implementation, but I do find it ironic
that what seems a conceptually neat and simple change manages to
generate such a lengthy debate.
There is general agreement that Cygwin is attempting to implement an
interface as close to Unix as possible, barring efficiency constraints,
while still using the underlying Windows file system.
It follows that in an empty directory "touch foo; ln -s foo bar; ls; ls -lL"
(and equivalent programmatic operations) should *not* show any evidence
of a file named bar.lnk, even if a Windows file of that name is used to
implement the link.
But Cygwin can never succeed in performing this kind of file mapping
perfectly; there are already difficulties with mixed-case (no-one
expects "touch foo; touch FOO; ls" to be Unix-consistent), and with
the treatment of .exe files which unfortunately breaks many makefiles.
So maybe we are worrying too much about hiding the implementation.
Just a thought - if a Windows directory contains both foo (a plain file)
and a foo.lnk shortcut, which should Cygwin open, stat etc. see?
Cliff Hones.
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -