Re: Possible Bug in 4.0 with warning()
- Posted by DerekParnell (admin) Aug 11, 2008
- 857 views
CChris said...
DerekParnell said...
This means that if the file contains a warning anywhere (and that is not excluded because of an ifdef statement)
Well, this is true only after dead ifdef branches are removed. An ifdef'ed out warning() never fires.
Yeah, that's what I said.