Re: continue keyword - since there is goto now, maybe reconsider continue?

[Ulrich Schmidt <u.sch.zw@...>]

Here my 2 cents:

Yes, if we are looking for new features, we will find a lot of ideas to 
implement. I like lua for his simple set of "features". What lua makes 
so lovely, is this clever chosen set of few features. And as less 
features a language has, as easy is it, to optimize the compiled code 
like luaJIT does.
For me it does not matter how i write my source code as long the 
compiler creates the same fast code.
In case, lua get more and more new "features", useful only in special 
cases, the interpreter/compiler footprint becomes bigger and bigger and 
optimizing compilers will fail more often. Thats no useful result for me.

Ulrich.

Am 09.01.2014 00:40, schrieb Jonas Thiem:
> Since there is now a working goto in Lua, I suppose there is no longer
> any technical reason why there is no continue.
>
> In case that's true, I would like to point out that goto as a
> continue-replacement isn't very nice:
>
> It needs twice the lines (goto statement + label), and you need to
> make up a unique jump label per loop if you got multiple loops in a
> function with such a continue workaround.
>
> Also, you can easily mix up your jump labels and suddenly jump into
> one of the other loops and generate non-obvious, huge bugs with that.
>
> What about natively supporting continue in an upcoming Lua version? I
> would be using it a lot, I do in all other programming languages which
> usually have it.