Re: Possible Bug in 4.0 with warning()
- Posted by twbeaty Aug 10, 2008
- 855 views
I think this is because warning() is a parse-time operation and not a run-time operation. This means that if the file contains a warning anywhere (and that is not excluded because of an ifdef statement), it gets added to the list of warnings that is displayed at program end. This happen regardless of whether or not the warning() is in the execution path.
If you need to provide a run-time message, then you still do that the traditional way.
... snip ...
Ah, okay. I must have misread the documentation on that. 
Still getting caught up on all the new goodies (and gotchas) of Version 4. That will work anyway, since I really wanted to give the value that was passed to count anyway. I was originally going to write my own warning system, but decided to give warning() a shot in order to save a little work.
btw, are there any plans for something along the lines of bugzilla, so we could mark this one closed?
- Travis.
