This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/38456] Suggestion: slight improvement of scoping rules
- From: "lc235951 at students dot mimuw dot edu dot pl" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 9 Dec 2008 19:09:45 -0000
- Subject: [Bug c/38456] Suggestion: slight improvement of scoping rules
- References: <bug-38456-17050@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from lc235951 at students dot mimuw dot edu dot pl 2008-12-09 19:09 -------
I know I can turn on warnings or use some tricks like UNIQUIFY(), but it's just
cumbersome with large macros.
I also know that changing the standard is considered "not done", but in this
case it cannot have any undesirable consequences, because any code exploiting
this behaviour is by definition incorrect (except for the case that you want to
get a random value from the stack in a really strange way). The only drawback
is that users may get used to it and try it with other compilers, so I proposed
a warning.
Well, but if you insist on such strict compliance then let it be so. After all
it's not that very important.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38456