AutoHotkey Community

Using a library is more complicated for programming beginners.

A Standard Library comes packaged with AHK. There is no room for complication if using the AHK installer. Too many built-in vars complicates things though ...

_________________

Recommended: AutoHotkey_L
Basic Webpage Controls

It doesn't seem worthwhile in terms of time and code/documentation size. That's reason enough for me.
It's not valid code. Obviously the value will be used in some context, and assigning it to a variable is the simplest context to demonstrate. If you're going to remove one assignment, to be fair you must also remove the DllCall assignment; so your point is moot.
I like that.

I think more useful constants than A_ScriptPID are things like A_CoordModeMouse, and other "missing" settings variables such as A_SendMode

Then, delete all date/time variables and use formatTime instead. After all, date/time variables save the same amount of code as A_ScriptPID would: one line

If you want valid code then,But the purpose of assigning a value to a variable is for later use. That means even `(A_ScriptPID) won't be necessary in this comparison.

The DllCall doesn't need to be assigned to a variable either.:roll:

It depends on the context. Some perefer to hold the value in a variable to use it in the traditional method, to use it multiple times, or to just make it readable. So in the code example, if the assignment, pid := DllCall("GetCurrentProcessID") is used for such usage, A_ScriptPID does not have to be assigned to a variable because it already has the value in it. FYI, this search result may prove how often a variable is used for a PID instead of the function call.

Also, the process id doesn't change until the script exits. So every time retrieving the PID, it is more rational to use the stored value in a variable rather than calling the function. And a value which does not change throughout the whole code execution is a good candidate to be a constant.

Off-topic, but the idea of A_HWND.A_Gui or A_HWND.A_GuiControl can be good and possible ? (same for script, name, path, ext and other)
I wonder if we can create "superglobal pseudo object" for have less built in variable and more generic word, and creat complexe variable like into an agglutinative language.

_________________
"You annoy me, therefore I exist."

Grouping some of the variables by topic might be useful in AHK v2 if it should move its focus towards a professional programming language. I'm not sure if it is required though or how much actual gain there would be.

One thing what comes to my mind is, it would help to reduce the possibility of naming clash. But this is not real world problem, as nearly nobody names the variables beginning with A_. In fact, I am not sure why all variables should be grouped in an arrray (in example as A.ScriptName). Consistency is the only reason, I think.

_________________
{1:"ahkstdlib", 2:"my libs", 3:"my apps", 4:"my license"}
--> Don't feed the troll! <--

Dunno, maybe I say too much stupid thing We can have a feature as this too , and it's customizable... However if we have A.Index then I have ton of doubt about peformance.

_________________
"You annoy me, therefore I exist."