Re: on allowing "int a" definition everywhere

Tim Rentsch <tr.17687@z991.linuxsc.com> writes:

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:

Tim Rentsch <tr.17687@z991.linuxsc.com> writes:
[...]
>

Not exactly.  There are things that can be done inside a
statement-expression that are not available inside nested
functions or lambdas.

>
And you're not going to tell us what those things are.

>
As a rule I don't have a lot of sympathy for people who are
too lazy to think for themselves.  I'm sorry to say that
class includes you a lot more often than would appear to be
warrented.

You seem not to be aware of how you come across.

Things like this make you appear arrogant.  You repeatedly make terse
and subtle statements (which are often, but not always, correct) that
would be trivial for you to expand on when you make them.  Instead, you
in effect assign homework to the rest of us.

It turns out that it's possible to jump out of a statement expression.
It was not obvious that that's permitted.  I very rarely use statement
expressions (among other things, they're non-standard), so I haven't
studied them in any detail.  But you expect me to think for myself and
infer that *obviously* they can be used that way.  I don't know how long
it would have taken me to figure that out if I had been motivated to
spend the time on it (it is mentioned in gcc's documentation) , but I'm
reasonably sure it would not have been worth the effort.  And it would
not have surprised me if gcc prohibited jumping out of a statement
expression.

I see from the rest of this thread that I'm not the only one who feels
this way.  Consider the possibility that the problem is not with
everyone else.

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */