Re: basename function in 4.3 cygwin

[Eli Zaretskii]

> From: Ronald Hoogenboom <RHoogenboom@irdeto.com>
> CC: "psmith@gnu.org" <psmith@gnu.org>, "bug-make@gnu.org" <bug-make@gnu.org>
> Date: Fri, 21 May 2021 15:17:53 +0000
> 
> As I said, possibly not a bug, but a change in functionality nevertheless.
> It is all about what you consider to be "the directory part" and this 
> consideration has apparently changed.

Not in the native port of Make, it didn't (I just tried).  Maybe in
the Cygwin port, which I don't have.

> The root cause of this is (as always) the dual meaning of a backslash: an 
> escape character or a path separator. Maybe a better way of escaping would be 
> single-quoting it. Note that in my real use-case, the character after the 
> backslash is a '?', which needs to be passed un-molested by the shell. I have 
> some weird experiences with single quoting in makefiles, though.

AFAIK, the Windows port treats the backslash as a quote character
where it makes sense (e.g., in wildcards).