Re: [Alephmodular-devel] 0.3 progress update ... warning count down

[Br'fin <br...@ma...>]

On Thursday, January 2, 2003, at 02:04  PM, Michael Adams wrote:
>
> Oh goody goody!  I imagine it took quite a bit of work
> to do that, but having warning free code is always
> nice.
>
Not too much work, mostly gruntwork and actually taking some time to 
appease the compiler. Now that most of the verbose but pointless 
warnings are out of the way any new ones become very obvious instead of 
being lost in the chaff. Yay!

> While your working in this area you may want to keep
> in mind a few brain dead compilers in this world that
> don't know about #warning.  I'll give you a hint: It's
> the compiler that most Windows people use.  Yep,
> that's right Microsoft's Visual C++ couldn't even get
> the preprocessor right (A1 only uses #warning in the
> Mac code not SDL).

> I don't know how you want to handle this.  I see two
> options.  Either, change the #warning's to #error's,
> which MSVC does understand, or put #ifdef around the
> #warning's.
>
> This wont become a major issue until we are actually
> trying to get it to work under Windows, but it's
> something to keep in mind and plan for.
>
> Again kudos on the warning elimination,
> Michael D. Adams
> mdm...@ya...
>
Thanks and thanks for the reminder. After a quick look at how my other 
favorite project (Bochs) uses warnings, I'll follow their example for 
now:

#ifdef __GNUC__
#warning blah blah blah
#endif

These are warnings, not errors. Little notes I've put in some spots of 
code that are dubious and should be redone at some point.

-Jeremy Parsons