you get the inevitable question, should *all* 'A_' variables be removed
I'm definitely leaning in this direction. I think it would probably be ok to leave some true constants, such as
A_PtrSizeand what else there might be. Note, for many of the BIV's, there is not just simple function substitution, eg, the hotkey BIVs, it needs restructuring the hotkey concept. Ofc, it is not going to happen .
- A_MsgBoxResult / A_InputBoxResult for AHK v1/v2.
It is not a good idea imo. (Surprised?)
ErrorLevel is positional
A_XXXResultwill have the same limitiation, as will
A_XXXResultwill either increase thread overhead or cause the same inconsitencies with interruptions as, eg,
A_ThisHotkey. The solution is to store
errorlevelin a variable when needed, so ofc,
errorlevelshouldn't be used in v2 (for
inputbox). The function(s) should return all that is needed. For example, something like this,
[text, errorlevel] := inputbox(...)
errorlevel := inputbox(textOut, ...)
where errorLevel symbolises the content which is currently stored in the variable
As a side note, I'd prefer
A_InputBoxResult(or another name) over
errorlevel, but as indicated above, it would just be a bit less worse.
Edit: to be clear, my use if the word should indicates my preference, not my demand.