AutoHotkey Community

Tank wrote:Sounds like a distinction without a difference. I can't think of any language where break/continue operate on an expression. I am not saying anything bout the value of doing it , only that no where else has that value made it into a language

Tank wrote:Return exists within a function to send a result back to the caller. It for this reason accepts an argument. Notice that return outside a function will not accept argument.

HotKeyIt wrote:

Code: Select all

Loop
  If (A_Index < 10), continue
  else if (20 > i:=A_Index), break

Code: Select all

Loop {
  continueif A_Index<10
  breakif (20 > i:=A_Index)
}

If (A_Index < 10), continue
else if (20 > A_Index), break, , i := A_Index

trismarck wrote:Perhaps this could be implemented then:

Code: Select all

If (A_Index < 10), continue
else if (20 > A_Index), break, , i := A_Index

If A_Index less than 20, break and set a few variables along the way.

if (A_Index > 20) { i := A_Index; some_var := some_value; break }

trismarck wrote:What I'm after is to _leave_ the first parameter of break as it is now and just allow an expression to be the second, non-existent parameter of break.

trismarck wrote:If break would allow expression mode (like return already does), the four-line if() statement above could be converted to just two lines:
Code: [Select all] [Expand/Collapse] [Download] (Untitled.txt)
Loop,
    if(a = b)
        break, , c++

Tank wrote:seems to indicate you just want to execute an unrelated expression on the same line?

tank wrote:sidenote: if this were allowed almost every function Sean ever wrote would have been 3 lines func name and opening handlebar 1 long statement and a closing handlebar. cause that fella abused multistatement for performance

Tank wrote:Unfortunately break seems to only operate when it is the only statement on the line of code so either IEA requires code change

• one of the predefined commands or whether the line is
• an expression or
• something else I have no idea about

        ++c, break

Break, ++c

Tank wrote: sidenote: if this were allowed almost every function Sean ever wrote would have been 3 lines func name and opening handlebar 1 long statement and a closing handlebar. cause that fella abused multistatement for performance

Tank wrote:How would multiple expressions be handled by your idea?

Coco wrote:

Code: Select all

b := "Hello World"
Loop {
   if (A_Index > 10 && dummy:=(true, i:=A_Index, a:=b))
      break
}
MsgBox %i%
MsgBox %a%

b := "Hello World"
Loop {
   if (A_Index > 10)
      break, , true, i:=A_Index, a:=b
}
MsgBox %i%
MsgBox %a%

Tank wrote:I mean the point of break is to stop here not to stop here and do these other things first
returns point is to go back to where you came from. with functions to return with a value

Coco wrote:It makes the code look more confusing

obj := ["aaa", "bbb", "aaa", "ddd", "eee", "aaa"]

for each, val in obj, Count := 0, found := false {
	if(val = "aaa")
		Count++
	if(Count = 3) {
		result := val, found := true
		break
	}
}
MsgBox, % found

for each, val in result, Count := 0, found := false {
	if(val = "aaa")
		Count++
	if(Count = 3)
		break, , result := val, found := true
}

for each, val in obj, Count := 0, found := false {
	if(val = "aaa")
		Count++
	if(Count = 3 && (1, result := val, found := true) )
		break
}

trismarck wrote:I'd consider the above to be more readable than doing all of the assignments inside of the if() statement:

trismarck wrote:Break is a command. Every command has parameters. Some of the parameters can be expressions. Expressions are evaluated before the command is called. From the point of view of how Autohotkey works, this is perfectly logical I'd say.

for k, v in ['ABC', 'DEF', 'GHI']
	if (v == 'DEF'), break() ; Command(s) can be called using function syntax -> this throws an error

obj := ["aaa", "bbb", "aaa", "ddd", "eee", "aaa"]

for each, val in obj, Count := 0, found := false {
    if(val = "aaa")
        Count++
} until (Count == 3, result := val, found := true)

MsgBox, % result

Coco wrote:It makes the code look more confusing... no benefit at all except for one-liner multistatements.