Re: Enforcing strict c99 compliance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jun 5, 2009 at 12:24, Ralf Wildenhues <Ralf.Wildenhues@xxxxxx> wrote:
> Hello Adam,
>
> * Adam Mercer wrote on Fri, Jun 05, 2009 at 04:42:08PM CEST:
>>
>> I have now got this working; on systems where AC_PROG_CC_C99 is
>> available this is used, otherwise the local copy is used. I have
>> noticed that AC_PROG_CC_C99 defaults to using -std=gnu99, is there a
>> way to use -std=c99 (i.e. without the GNU extensions)?
>
> Not OOTB.  Typically, strict compliance creates more problems than it
> solves, for software that aims to be portable.

Thanks Ralf, our idea for using strict c99 was for portability
reasons. I'll guess we'll hold off that idea.

Cheers

Adam


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf


[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux