Sender:	rich AT phekda DOT freeserve DOT co DOT uk
Message-ID:	<3E5E3546.278840F7@phekda.freeserve.co.uk>
Date:	Thu, 27 Feb 2003 15:56:54 +0000
From:	Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer:	Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language:	de,fr
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: perror
References:	<20030227150458 DOT GA3476 AT kendall DOT sfbr DOT org> <1046360051 DOT 30750 DOT 3 DOT camel AT leeloo>
Reply-To:	djgpp-workers AT delorie DOT com

Hello.

Tim Van Holder wrote:
[snip]
> As for the blank, the Linux man page isn't very clear either:
> 
>   First (if s is not NULL and *s is not NUL) the argument string s is
>   printed, followed by a colon and a blank.  Then the message and a
>   newâ??line.
> 
> This is decidedly unclear about the fate of the colon and blank if
> s is null or empty.

If in doubt, look at a standard. Here's what draft 7 of new POSIX says:

"First (if s is not a null pointer and the character pointed to by s is not
the null byte), the string pointed to by s followed by a colon and a <space>.

Then an error message string followed by a <newline>."

I don't have time to look at C99 right now. But POSIX embraces that, so it
should be the same.

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]

- Raw text -