FidoNet Echomail Archive
aust_c_here

<<< Previous Index Next >>>

From: Roy McNeill
To: Frank Adam
Date: 1997-08-20 21:09:00
Subject: warnings

Hi Frank

 FA> Thanks, i always have that switched on. But your reply did make me go and
 FA> check again and i found an option, which i've never touched or looked at
 FA> before.
 FA> To force inline functions out of line.
 FA> That was it, i can trace it now. Shame about all those printfs i've wasted
 FA> fixing the bug .:-) Worse, i should've thought of it, one of the first
 FA> lines i put into a C++ program is #pragma warn -inl to turn off that stupid
 FA> warning.
 FA> Oh well, learn something every day.

I try to leave all warnings turned on, even the irritating ones -
they tell me when I'm being lazy.

One exception: a program that was pretty well mature had some
Unused Parameter type warnings that looked a bit too hard to get
rid of (they varied weirdly with some global #define's). In that
case, I put the warning turnoffs just before the function, and
turned the warnings back on again immediately after. The warnings
then stay active where needed, and the #pragma statements are nice
and visible near the offending event, serving as a reminder.

Cheers

--- PPoint 1.88
 * Origin: Silicon Heaven (3:712/610.16)
SEEN-BY: 620/243 622/419 632/107 360 633/154 260 267 270 371 373 635/728
SEEN-BY: 638/102 639/252 640/820 670/218 711/410 413 430 953 963 712/0 62
SEEN-BY: 712/302 311 407 505 506 517 555 619 848 888 713/317 714/930 800/1
@PATH: 712/610 888 506 711/410 633/260 632/360 635/728 633/267


<<< Previous Index Next >>>