On Thu, 17 Aug 2006, Corinna Vinschen wrote:
> On Aug 17 09:59, Igor Peshansky wrote:
> > Actually, as Gareth mentioned, *Cygwin* allows colons in file names on
> > managed mounts. So, at the very least there'd be confusion of whether
> > c:\\TEMP is a directory TEMP in the root of the C: drive, or a file named
> > 'c:\\TEMP' in the current directory on a managed mount...
>
> Since colons are perfectly valid characters on POSIX file systems,
> there's no reason to generate a special case for Cygwin. The problems
> generated by using such filenames are identical on all these OSes.
I was simply pointing out that in case of Cygwin, if the build happens to
run on a managed mount (which emulates a true POSIX file system), having
DOS paths in the Makefile is ambiguous anyway. This is in addition to any
(non-)problems introduced by colons and backslashes.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
