As I said, I would haven't yet tried compiling FLTK with those options ---
personally I don't think it would even make it.
>
> > -Wall
> > -ansi
> > -pedantic
> > -ggdb
>
> Do you know which option is triggering the noise? I'd guess "pedantic"
> but I don't know for sure.
Yes ---
-pedantic
Issue all the warnings demanded by strict ISO C and ISO C++; reject
all programs that use forbidden extensions, and some other programs
that do not follow ISO C and ISO C++. For ISO C, follows the
version of the ISO C standard specified by any -std option used.
Valid ISO C and ISO C++ programs should compile properly with or
without this option (though a rare few will require -ansi or a -std
option specifying the required version of ISO C). However, without
this option, certain GNU extensions and traditional C and C++
features are supported as well. With this option, they are
> Of those only Wall and ggdb are options I use often... What do you gain
> by using ansi and pedantic here? I'm just wondering...
>
conformity to ANSI standard (e.g. it should work with all ANSI C/C++ compilers.
The GNU Compiler is nice in that non-standard (non-ANSI) library calls such as
strdup will blink because it's not ANSI. I suppose a `lint' check would do the
same.
>
>
> SELEX Galileo Ltd
> Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS=
> 14 3EL
> A company registered in England & Wales. Company no. 02426132
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************
>
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
