From: Sam Roberts <sroberts@...>
Date: 2006-04-27T14:11:49+09:00
Subject: Re: possible defect in array.c

Quoting nobu@ruby-lang.org, on Thu, Apr 27, 2006 at 11:55:17AM +0900:
> Hi,
> 
> 2006/4/27, Sam Roberts <sroberts@uniserve.com>:
> > Are you sure? It appears to support non-standard extensions in both C99
> > and C89 dialects. I'm not complaining, the extensions are useful, but
> > just because gcc compiled it doesn't mean its standard C, of any
> > particular dialect.
> 
> Well, you're correct it has its own extensions not only C99 and C89
> standards, and you need -pedaintic-errors option to let gcc be strict
> with them.  But it doesn't croak if -std=c99 is also given, and I
> thought it is the default in gcc4, IIRC.

I think you are right about that.

> I meant that change about the based standards.

Yes, I see your point, the particular thing he was doing is standard
now, not a gnu extension.

I think gcc allowed it well before 1999 though! I tend to stick to the
older standard, porting from C99 to C89 would be awful, and there are
still many older compilers around for embedded system. It appears to
me that ruby src doesn't assume a C99 compiler currently, I hope it
will continue to build with C89.

Cheers,
Sam