I do use that for platform and symbol warnings when third party code is involved.
Dave. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, 1 June 2004 8:53 a.m. To: [EMAIL PROTECTED] Subject: RE: [DUG] Weird Delphi Warning If you don't do it already, you can use {$HINTS ON|OFF} or {$WARNINGS ON|OFF} in your code to explicitly prevent a particular code warning from appearing in the list. I'm just much happier seeing a message saying 0 Hints, 0 Warnings, rather than always expecting to see a list of warnings even if I ignore them. If the list remains, it's too easy to miss a new warning that could be more significant, IMHO. I'll stick my neck out further and say I still believe it is possible to code so that no warnings/hints are raised, even if it doesn't look like the most obvious way to write it. To me, having a 100% clean compile is preferable. Cheers, Conor -----Original Message----- From: David O'Brien [mailto:[EMAIL PROTECTED] Just ignore that particular warning, as I can't see any reason for it. As I say, almost identical code (i.e. Result defined similarly) doesn't produce the warning. I never allow other hints or warnings to remain. Just that one makes no sense and seems random. Dave. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Do you explicitly ignore that specific warning or just ignore the compiler warning list? We won't let our developers check in code with hints or warnings... _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi _______________________________________________ Delphi mailing list [EMAIL PROTECTED] http://ns3.123.co.nz/mailman/listinfo/delphi
