This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: change in behavior of make from 3.80 to 3.81


On 17 August 2006 15:25, 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,

  Well, kind of, and kind-of not:

http://www.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html

 3.170 Filename Portability

Filenames should be constructed from the portable filename character set
because the use of other characters can be confusing or ambiguous in certain
contexts. (For example, the use of a colon ( ':' ) in a pathname could cause
ambiguity if that pathname were included in a PATH definition.)

  But I guess that's a SHOULD, not a MUST.


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]