AutoHotkey Community

I found a situation where Goto is the best option.
The Tray menu on Autohotkey for Pocket PCs has two items that don't work (Windows Spy and Help) and it's missing some things that would help alot. I can't invoke the software keyboard while in the ListLines so I wanted to add shortcuts to the other pages (like KeyHistory). I decided to make a file to include at the top on new scrips that has the new menu in it as well as the labeles in it. I do not want the included file to end the AutoExecute section. The Best way I could think of to have both was to Use Goto to Skip over the labels.

That way the scripts that use it can still have stuff happen after start up

Why not GoSub followed by Return?

_________________
"Read the manual. Read it again. Search the forum.
Try something before asking. Show what you've tried."

Antonio França
My stuff: Google Profile

Because it should not return. If I used Gosub then it would come back to before the labels and I would need a return to end the AutoExecute section so the labels arn't executed.
If I'm Wrong Please post how you would accomplish this.

Yes, I know. Once again: why not? I didn't get it.

_________________
"Read the manual. Read it again. Search the forum.
Try something before asking. Show what you've tried."

Antonio França
My stuff: Google Profile

Well to my knowledge AHK only "remembers" one previous label.
So....


Like I said I THINK this is what he is talking about.

Wheres replacing the GoSub,Third with GoTo,Third would allow the message box to show.

_________________
Check out the new AHK forum competition!

@Ace Coder: You are incorrect.
This code shows "Start, Second, Third, Do I show?", as expected.

_________________
"Read the manual. Read it again. Search the forum.
Try something before asking. Show what you've tried."

Antonio França
My stuff: Google Profile

Simpler Example
If you change the GoTo to GoSub the script automatically exits without pressing Escape.

Yes, so you would be forced to use GoTo only if the included file uses GoTo the exact same way. Cyclic logic. Anyway, I can't force you to use GoSub. I hope I never get one of these codes to debug.

_________________
"Read the manual. Read it again. Search the forum.
Try something before asking. Show what you've tried."

Antonio França
My stuff: Google Profile

If you can show me a way to #include "Menu, Tray" commands and their labels without using GoTo I'll Consider it. (Unless you idea is to use two includes one in the Autoexecute section and one after it. )

Gonorrhea ! Goto, aDoctor

I myself don't mind goto, i do use it every now-and-then, here-and-there.
don't people not like it because it can make code confusing? how? whats so hard to grasp about "okay, if (today is monday the 5th): "go to" the airport and get a 1-way ticket to Jamaica."
on irc, you'll find that most people (noobs, not regulars) find gosub more confusing, why should you Return just to Return (which you do 90% of the time anyways)?

Instead of going back to do nothing, just don't go back and do nothing.

_________________
rawr. be very afraid
*poke*
Note: My name is all lowercase for a reason.
"I think Bigfoot is blurry, that's the problem. It's not the photographer's fault, Bigfoot is blurry. So there's a large, out-of-focus monster roaming the countryside."

Instead of pulling the new menu and labels into the tray script how about pulling the tray script into new menu and labels, i.e. #include the tray menu script in place of GoTo? That would save a line by eliminating the extra label.

As for the theoretical argument concerning GoTo, there is nothing inherently evil about it; however, it is widely abused and used in places where an alternative would be better. GoTo doesn't create bad programs: bad programmers create bad programs. The reason I oppose the use of GoTo (and Gui, Destroy) on these forums is due to the target audience of AHK. This language is intended for non-technical users, the vast majority of whom will never grasp the more powerful and often more readable constructs like loops, blocks, branches, and functions by continually using GoTo as a crutch to support bad program design. For AHK scripters, eliminating GoTo is a great learning exercise, even when it doesn't produce more efficient code.

Finally, since the title of the thread is a situation where GoTo is necessary, I've found it useful to break out of nested loops. Some languages have explicit commands for that, but in AHK GoTo can be simpler than checking a variable in every loop just to break out of the inner-most.

+1 to jaco06046

_________________
"Read the manual. Read it again. Search the forum.
Try something before asking. Show what you've tried."

Antonio França
My stuff: Google Profile

There is no need for GoTo in these examples. And there is less code.

It is actually proven, that GoTo is never neccessary:


But GoTo sometimes helps producing shorter code or increase it´s readability. see:http://kerneltrap.org/node/553/2131