Date: Thu, 13 Jul 2000 14:22:24 +0200 From: Sheldon Hearn <sheldonh@uunet.co.za> To: nbm@FreeBSD.ORG Cc: mark@thuvia.demon.co.uk, freebsd-bugs@FreeBSD.ORG Subject: Re: bin/5297: make incompatibility with System V style variable substitions Message-ID: <82261.963490944@axl.ops.uunet.co.za> In-Reply-To: Your message of "Thu, 13 Jul 2000 04:12:16 MST." <200007131112.EAA82895@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 13 Jul 2000 04:12:16 MST, nbm@FreeBSD.ORG wrote:
> State-Changed-From-To: suspended->open
> State-Changed-By: nbm
> State-Changed-When: Thu Jul 13 04:11:35 PDT 2000
> State-Changed-Why:
> This PR received feedback, and a patch has been proposed. Leave it open
> for others to look at.
I haven't spent an enormous amount of time looking at the POSIX.1
specification for make(1), but it certainly seems to me that it does not
define correct behaviour for an empty subst1 in
$(string1[:subst1=[subst2]])
or
${string1[:subst1=[subst2]]}
So we're pretty much left to our own devices. I think it makes sense to
see how OpenBSD, NetBSD and BSD/OS are doing this before looking at
System V and friends.
However, even if we found that all the other BSD's exhibit the current
behaviour, we'd be hard-pressed to justify it. I certainly can't find
much use for the way make(1) behaves now.
Mark, you wanna tackle the fact-finding mission?
Ciao,
Sheldon.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?82261.963490944>