This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Scopes in which __label__ can appear
Gabriel Dos Reis <gdr@integrable-solutions.net> writes:
> | > In parallel to your argument, there is no particular reason to reject
> | > the above.
> |
> | So the __label__ in this example has no effect at all?
>
> Basically, I'm saying yes. It would be a no-op.
I don't like that, I think it'd be confusing and surprising to users.
I'd much rather either reject the code or narrow the scope of the
label (and therefore reject the code because the label isn't in scope
for the goto).
Also, from an implementation point of view, either of my preferred
options is cleaner than what you are suggesting.
zw