I think that `continue` is a well established flow control keyword in programming by now. It's a little bizarre having to show its worth by different examples like it's 1989.
In my opinion, Lua would only benefit from it.
-- with reagrds, Alexander Ch
`continue` is useful if you're working with input checking. For example you're checking user input through stdin, you want to check if it's valid if not do the input again.
while true doio.write "Please input an ascii code: "local input = io.read()
if not input:match "^%d+$" thenprint "Not a number"continueendlocal ok,ch = pcall(string.char,tonumber(input))if not ok and ch thenprint("Failed to parse code:",ch)continueend
On Fri, Mar 17, 2023, 22:48 Steven Hall <email@example.com> wrote:
I’ve found that if-statement nesting can be easily removed by re-evaluating (refactoring if you want a better buzz-word) your logic.
You might want to come up with a more convoluted example as one can eliminate the “continue” easily here and many other such trivial examples.
for i = 1, 10 do
if i % 2 ~= 0 then print (i) end
> for i = 1, 10 do
> if i % 2 == 0 then continue end
> print( i )
> This should really help to reduce unnecessary if-statement nesting inside loops.