X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; q=dns; s=default; b=vKc2aHkEwPc0y4aFNc0KQZHFllK+z
	7rzbI4mZrRINuAthqbgcEAdVQ+IedoKVjVTb7aSs0WCKla1HKzp7s7ILavb9oorp
	fPpn6aZsqD+vG1NaxRszAYCZJT57CkBDZjcEZ5RKh45AP7AZWZKx5/79mXg6Bkiu
	rK3QyHK0AyfK6M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-transfer-encoding
	:mime-version; s=default; bh=gsyBE+ZUkTAlgfbafeta8K7MGT8=; b=lg8
	sNmyX12jlRLzhYrBpa/209uDPQk49Tsq0I+JMRU4HIHyY8WCiEvWadoZISaZrEiw
	S+bu+I84wyqqsPPnE/XWcBfHzUik1ZsEDOFJPsxBoDdkO+YEl+3KFDP9zYB5foTB
	lEAEANSzpYJBS+Lkslwn23cgR0Pqb2iRoQqY4R7I=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=0.8 required=5.0 tests=BAYES_40,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,MIME_BASE64_BLANKS,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=H*r:172.16.0, Greetings, Hx-spam-relays-external:172.16.0.1, H*RU:172.16.0.1
X-HELO: outmail148154.authsmtp.co.uk
From: David Allsopp <David DOT Allsopp AT cl DOT cam DOT ac DOT uk>
To: cyg Simple <cygsimple AT gmail DOT com>, "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: RE: Bug Report: Regression in Cygwin 2.11.0-1
Date: Sun, 2 Sep 2018 07:31:59 +0000
Message-ID: <E51C5B015DBD1348A1D85763337FB6D901ADFF6FE4@Remus.metastack.local>
References: <BL2PR16MB096125DC7F302700C5DE88C0C80E0 AT BL2PR16MB0961 DOT namprd16 DOT prod DOT outlook DOT com> <pmdgjr$9q9$1 AT blaine DOT gmane DOT org> <20180901155435 DOT GL6350 AT calimero DOT vinschen DOT de> <E51C5B015DBD1348A1D85763337FB6D901ADFF2257 AT Remus DOT metastack DOT local> <1177432276 DOT 20180902005232 AT yandex DOT ru> <921ff66e-cc22-5df2-db16-5f9cc1193185 AT gmail DOT com>
In-Reply-To: <921ff66e-cc22-5df2-db16-5f9cc1193185@gmail.com>
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
X-Server-Quench: 48fbe8e1-ae82-11e8-8e1a-9cb654bb2504
X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse
X-AuthRoute: OCd1ZAARAlZ5RRob BmUtCCtbTh09DhZI RxQKKE1TKxwUVhJU L0JGL0JXPR1GBEcB AXloDhRLUl1wUXN1 YwBSbw9dYARMXgZ0 UUhMXFBTFhtpABge BBsBU1c1fwdBH38H IUZnV3BcXwpzdUJ1 DEpcQz9TbTJhdTFK WEJFdgIBeB5CKx4U d1ksBnUIZTdVZH9g QxkJEmJ5FyhQYB5Y WgYXMQBae0sEBDMn XBEFG30uGwUuVios LhpucBhFRQBJdxxa
X-Authentic-SMTP: 61633634383431.1039:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 213.105.212.114/25
X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system.
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id w827WLnS019837

cyg Simple wrote:
> On 9/1/2018 5:52 PM, Andrey Repin wrote:
> > Greetings, David Allsopp!
> >
> >>> In terms of this OCAML build system problem:
> >>>
> >>> Please fix your build system.  Do not mix POSIX and Win32 paths, use
> >>> POSIX paths only.  Backslashes are *no* drop-in replacement for slashes.
> >
> >> The "problem" for us is more subtle than this. The program which is
> >> generating that path is not a Cygwin executable, so it is correctly
> >> combining a path it has been supplied (the ../stdlib which has been
> >> supplied via Cygwin's make) with a filename, so it uses a backslash.
> >> It's been on my TODO for years to enhance to understand that the
> >> program it's supplying the path back to is a Cygwin executable and so
> >> sort it out properly but, well, we're a small number of maintainers! That
> said, WSL is forcing us to address it properly...
> >
> > You CAN just send back forward slashes. Windows don't care.

That's not strictly true, as mkdir foo/bar will demonstrate in a command prompt (it is almost true when dealing with the Windows API). However, IMO, one looks like a Unix programmer who doesn't really understand Windows when your programs visibly use forward slashes everywhere. 

> > If any program would choke, it would be that program's problem after all.
> 
> Certainly not "that program's problem". The problem becomes mine and yours
> as we've not followed the design of the program.  While Windows at the
> moment doesn't care there is always the possibility that some fix could break
> that since the documentation states to use \ in paths and not /.  So while we
> "CAN just send back forward slashes" we need to be prepared for the outcome
> if something changes in an update to the OS and breaks the assumptions based
> on observed behavior rather than the documented behavior.

Just as an aside, the use of slashes is documented: see Kuhne's compulsory reading on the subject at https://blogs.msdn.microsoft.com/jeremykuhne/2016/04/21/path-normalization/ and also the notes in MSDN (https://docs.microsoft.com/en-gb/windows/desktop/FileIO/naming-a-file#maximum-path-length-limitation) which do mention that normalisation of / to \ in the API is not an accident.


David


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple