I think better to use the context of the english language for a
pre-condition checked after:
until Condition() { ... }
Or maybe just exactly mimics for, but does not test until after one run of
the enclosed block:
until Init(); Condition(); PostAssignment() { ... }
On Friday, 11 May 2018 01:29:55 UTC+3, Michael Jones wrote:
>
> So sorry to learn of your mistreatment. I've never been struggled in an
> anti-do-while cultural revolution, though I can imagine the lasting
> emotional harm.
>
> I always* thought that C's "do {stuff} while (cond);" was a victim of
> syntax. The cond is far away and hidden from the do. An idea from the Go
> line of reasoning could be like this:
>
> for preCondition; beforeCond; updateStatement; afterCond {stuff}
>
> The argument for this would be just one looping construct, capable of a
> pre and post conditions, all set out at the start. It might be pretty
> enough to escape the thuggery of the past. ;-)
>
> Michael
>
> On Thu, May 10, 2018 at 1:32 PM Rob Pike <r...@golang.org <javascript:>>
> wrote:
>
>> There is a widespread dislike of do-while in C. Pretty much every time
>> I've wanted it, my code reviewer made me take it out. I agree it has its
>> place but it's one of those style things that social pressures seem to
>> force. I would not be the one to try to argue for its return; I couldn't
>> handle the backlash.
>>
>> -rbo
>>
>>
>
> --
> Michael T. Jones
> michae...@gmail.com <javascript:>
>
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
