Date: Fri, 20 Dec 2024 15:11:24 +0200
On Fri, 20 Dec 2024 at 15:06, Jan Schultke <janschultke_at_[hidden]> wrote:
>
> You have probably found this in the draft already at this point, but here it is:
>
> https://eisenwave.github.io/cpp-proposals/break-continue-label.html#opposition-to-n3377
> contains the full set of criticism towards the N3377 syntax. There are
> too many to write it all out here.
"Now, decades after the fact, and a million files later, we need to
invent our own, novel syntax just for labeling loops and switches? No,
we don’t!"
Yes, we do. It's a name of the loop, scoped to that loop, not a generic label.
"This is a readability issue; with the exception of goto and labels,
function bodies can be understood by reading them from top to bottom."
The claim is not correct for member functions defined inside a class
definition before data member declarations.
>
> You have probably found this in the draft already at this point, but here it is:
>
> https://eisenwave.github.io/cpp-proposals/break-continue-label.html#opposition-to-n3377
> contains the full set of criticism towards the N3377 syntax. There are
> too many to write it all out here.
"Now, decades after the fact, and a million files later, we need to
invent our own, novel syntax just for labeling loops and switches? No,
we don’t!"
Yes, we do. It's a name of the loop, scoped to that loop, not a generic label.
"This is a readability issue; with the exception of goto and labels,
function bodies can be understood by reading them from top to bottom."
The claim is not correct for member functions defined inside a class
definition before data member declarations.
Received on 2024-12-20 13:11:42