AutoHotkey Community

[majkinetor]

After several personal messages with the author, I wrote this article to adress some issues in the current AHK language.

Then I explain script merging technique, several times discussed on the forum already.

In the archive is the 30 page article and examples used as a proof of a concept.

I hope that you will find this useful.

Download                          Read

Note about included scripts:

1. Favmenu is Open/Save dialog enhancer. It will change the directory in any standard open/save dialog. For more details and full documentation see: http://www.ghisler.ch/wiki/index.php/Features_and_Installation

2. Editor is Favmenu's menu editor.
3. Parent is merged script that contains 1 & 2

_________________

[majkinetor]

2 corrupt

[corrupt]

Hi majkinetor,

An interesting read . In general, I don't have much of a need to merge scrips since I usually create scripts for very specific purposes. For this reason, I have a menu script that launches/terminates specific scripts when needed that is activated from a hotkey.

It sounds like your work could provide a solid foundation for creating a script that can parse existing scripts and create plugin compatible scripts then optionally merge them with other scripts. I'm sure many people would be interested in such a script. This way someone could pick a few of their favorite scripts and have a master script automatically generated for them .


A few comments on your well documented Constructive Language Criticism:

labels - not being restricted on where jumps are allowed allows more flexibility in writing scripts. The responsibility is on the person creating the script to avoid jumps that may cause internal issues

whitespace - The example you gave is a fairly obvious syntax error to me but may not be obvious to others... AFAIK this alternative works ok:
MyFunction(){
global
...
}

Your variable example: s := s . "new text" . p is valid so why not just use that method if you find the difference to be trivial?

You may be overlooking that the 2 ways of assigning variables play an important role in syntax for being able to create/modify variables dynamically.

arrays - I agree that the current global/local declarations in functions aren't very flexible when using functions but I'm guessing that it likely won't be an issue when true arrays are implemented. Adding syntax as a workaround doesn't seem worthwhile IMO.

Strings - There are a few methods available for accessing string characters at a specific offset. Wrapper functions for StringMid, StringLeft, etc... would be nice but are simple to add to a script.

Commands with the same meaning - I also prefer to use expressions in most cases but the simplicity and flexibility of the other commands is also very appealing. Actually, it was the simplicity of those commands that attracted me to start using AutoHotkey to begin with. I think it's much easier for beginners to learn and allows flexibility in various commands.

[majkinetor]

hi corrupt

[majkinetor]

I added page to my server so if you want to read you can click the Read link in the first post. To download with included scripts that are proof of a concept, use Download link.

I also updated Wiki->Documentation->Tutorials: http://www.autohotkey.com/wiki/index.php?title=Main_Page
_________________

[Tester]

I enhance this idea to modules auto-search and auto-load discussed here

Regards

[majkinetor]

Sorry, I didn't see your post until today.

I will check it out.
_________________

[Tester]

No problem. I haven't not yet time to write code for files parsing, so at this time this is not yet working algorithm - it is only idea.
Regards.