Suggestions

David Bryan D.J.Bryan at cranfield.ac.uk
Fri Apr 28 15:00:43 BST 2000


In message <pK4jaDAo7YC5Ewoc at mk-net.demon.co.uk>
          Tony van der Hoff <OSLib at mk-net.demon.co.uk> wrote:

> >> How do we recognise C99? Does the standard define a compile-time flag?
> >> Or will <stdbool.h> define a macro? 
> >> 
> Oh, yes! |__bool_true_false_are_defined| <g>
> 
> Let no-one take the piss out of OSLibInclude$Path again ;-)
> 
> >> Has anyone got a URL for the standard, please?
> >
> >http://anubis.dkuug.dk/JTC1/SC22/open/n2620/
> >
> Thanks for that, David.
> "Working draft, 1997-11-21"; is that what was ratified as C-99?

Oops, v. sorry, no.  I should have said

  http://anubis.dkuug.dk/JTC1/SC22/open/n2794/

or

  http://anubis.dkuug.dk/JTC1/SC22/WG14/www/docs/n843.pdf.gz

which was the Final Committee Draft, and what was voted on.  While
the oh-so-short macro |__bool_true_false_are_defined| is still
there, the nature of |bool| was changed quite dramatically.  C now
gains a proper boolean type, |_Bool|.  <stdbool.h> then defines
|bool| to expand to |_Bool|.  Anyway, as Jonathan said, the check
would be for the version of C the compiler is for, not whether
<stdbool.h> has been included.

-- 
David Bryan




More information about the oslib-user mailing list