> Any compiler that does not produce the correct code has a bug - baring
> any error messages.
How do you define 'correct'?
The compiler produced 'correct' code according to the ISO C standard. It
has no way of knowing what's 'correct' if you define that as meaning the
_intention_ of the programmer, even when they write incorrect source code.
The code posted was broken - or at least the assumption about the results
was incorrect. The compiler's behaviour was perfectly OK.
If you have code to enable a 'Do what I meant, not what I wrote' feature in
gcc, I'm sure we'd all be glad to see it - I know I've needed it before now :)
Gcc does have some warnings of the 'You wrote this; are you sure you didn't
mean something else' variety. Perhaps adding a warning for this situation
would be possible - perhaps not. But that wouldn't be a bug report, that
would be a feature request. And I believe gcc-3.0 is in feature-freeze
_______________________________________________ Axp-list mailing list Axpemail@example.com https://listman.redhat.com/mailman/listinfo/axp-list
This archive was generated by hypermail version 2a22 on Sat May 5 06:18:13 2001 PDT
Send any problems or questions about this archive to firstname.lastname@example.org.