gpsd-dev
[Top][All Lists]
Advanced

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

Re: [gpsd-dev] several messages


From: Gary E. Miller
Subject: Re: [gpsd-dev] several messages
Date: Mon, 15 Aug 2016 17:20:04 -0700

Yo Greg!

On Mon, 15 Aug 2016 20:13:17 -0400
Greg Troxel <address@hidden> wrote:

> Fred Wright <address@hidden> writes:
> 
> >> The other thing that works with gcc and clang is to add
> >> --std=c99.  I am not sure if that is duplicative with the define
> >> you mentioned, but it seems to be the normal way to tell the
> >> compiler to disable gcc extensions and to follow the C99 standard
> >> as strictly as it can.  
> >
> > However, that's specific to gcc/clang.  The point of the POSIX 'c99'
> > command (when it exists) is to hide such details.
> >
> > http://pubs.opengroup.org/onlinepubs/9699919799/utilities/c99.html  
> 
> Totally fair, but in configure.ac, if you don't find c99, but do find
> clang or gcc, and add --std=c99, that helps.
> 
> On NetBSD from 5 onward, there is /usr/bin/c99:
> 
> #!/bin/sh
> exec /usr/bin/cc -std=c99 "$@"
> 
> OS X 10.9 has a /usr/bin/c99 that is documented to conform to POSIX.
> 
> So I agree it is worth checking for c99 as you say.

Two things. 

It fixes a problem I have not seen yet.  Yes my head is in the sand.

I puts a cap at c99, not a floor at c99.

And sadly, I'm finding a ton of code that is not C99 compliant, many
patches in progress.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
        address@hidden  Tel:+1 541 382 8588

Attachment: pgpQaZXvIKLMV.pgp
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]