This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Documenting tools necessary for GCC [draft]
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Fergus Henderson <fjh at cs dot mu dot OZ dot AU>
- Cc: obrien at freebsd dot org, gcc at gcc dot gnu dot org
- Date: Sun, 01 Jun 2003 01:26:10 -0700
- Subject: Re: Documenting tools necessary for GCC [draft]
- References: <200305291727.NAA06347@caip.rutgers.edu><20030530171122.GA90937@dragon.nuxi.com><87llwmi8jb.fsf@egil.codesourcery.com><20030601075857.GA26913@ceres.cs.mu.oz.au>
Fergus Henderson <fjh@cs.mu.OZ.AU> writes:
> On 01-Jun-2003, Zack Weinberg <zack@codesourcery.com> wrote:
>> "David O'Brien" <obrien@FreeBSD.org> writes:
>>
>> > I'd really like this to state a POSIX compliant shell, and list the exact
>> > POSIX spec (and year) that OS's must adhere to.
>>
>> Not good enough. [...] you can find blatant
>> semantic or even syntactic incompatibilities between shells or Make
>> implementations that claim to be POSIX compliant.
>
> Sure, but you can find blatant incompatibilities between different C
> compilers too... why is writing shell code or make code that conforms
> to the POSIX spec any harder than writing C code which conforms to
> the C standard?
The C standard gives an implementor far less wiggle room.
zw