Mirsad Todorovac wrote:
However, maybe there should be a third result of a test, 'warning'; which would test non-portable behavior?
What a coincidence, just yesterday I implemented `WARN' as a test suite flag!
And second, shouldn't compiler *WARN* me about accessing the value of non-initialized variable with IN operator? I've tried and even with -Wall gpc was quiet.
It's a known issue that the uninitialized-warnings don't work with global variables and some non-simple types (strings, sets, ...). I hope we can fix this sometime (but currently, there are more important issues) ...
Frank