Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Nov 2001 14:06:42 -0500 (EST)
From:      Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
To:        Bill Fenner <fenner@research.att.com>
Cc:        current@freebsd.org
Subject:   Re: buildworld breakage during "make depend" at usr.bin/kdump
Message-ID:  <200111011906.fA1J6gJ26843@khavrinen.lcs.mit.edu>
In-Reply-To: <200111011840.KAA23489@windsor.research.att.com>
References:  <200110312159.f9VLx1I45943@bunrab.catwhisker.org> <200111010549.fA15nPG47227@bunrab.catwhisker.org> <200111011614.fA1GE8P25519@khavrinen.lcs.mit.edu> <200111011840.KAA23489@windsor.research.att.com>

next in thread | previous in thread | raw e-mail | index | archive | help
<<On Thu, 1 Nov 2001 10:40:07 -0800, Bill Fenner <fenner@research.att.com> said:

> Perhaps in breaking backwards compatability with gawk, but
> IEEE Std 1003.1-200x says:

> Guideline 6:        Each option and option-argument should be a separate
>                     argument, except as noted in Section 12.1 (on page
>                     199), item (2).

> I don't think that any of the exceptions in section 12.1 item (2) apply
> to awk's -v argument.  POSIX *permits* but does not *require* the
> gawk behavior.

I don't think that this is the intended interpretation.  I believe
that this is intended to prohibit programs (like old-style `cc' and
`tar', for two very different examples) which require options or
option-arguments to be in a single argument (e.g., `-L/foo/bar' or
`xvf').

See section 12.1, paragraph (2)(c):

# c. Notwithstanding the preceding requirements on conforming
# applications, a conforming implementation shall permit an
# application to specify options and option-arguments as a single
# argument or as separate arguments whether or not a <space> is shown
# on the synopsis line, except [XSI case deleted]

What this is saying is that users are supposed to separate all
arguments (or not) according to how they are shown in the Standard,
but with few exceptions the implementation is not allowed to require
this.

-GAWollman


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111011906.fA1J6gJ26843>