X-Spam-Check-By: sourceware.org From: "Dave Korn" To: Subject: RE: change in behavior of make from 3.80 to 3.81 Date: Thu, 17 Aug 2006 15:27:23 +0100 Message-ID: <00e801c6c209$419e85c0$a501a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20060817142510.GH20467@calimero.vinschen.de> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com 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/