[v2.0.2] Launcher doesn't handle #requires properly Topic is solved

Report problems with documented functionality
white-ah
Posts: 8
Joined: 11 Jan 2023, 09:47

[v2.0.2] Launcher doesn't handle #requires properly

Post by white-ah » 14 Jan 2023, 13:33

It seems launcher.ahk doesn't handle #requires directives very well:
  • It seems it is not, or not well, adapted to the recent changes to the #requires directive (support for operators < <= > >= = and additional keywords)
  • "v" before version number was always optional since introduction 1.1.33 but launcher assumes it is mandatory
  • Launcher assumes it is mandatory that something other than white space directly follows the first digit of the version number. This is not the case for example with these lines which launcher cannot handle:
    • #Requires v1
    • #Requires v2
  • Launcher assumes that a comment on the #Requires line starts at a semicolon instead of at a semicolon preceded by white space

white-ah
Posts: 8
Joined: 11 Jan 2023, 09:47

Re: [v2.0.2] Launcher doesn't handle #requires properly

Post by white-ah » 14 Jan 2023, 16:50

See also this issue reported by someone else:
https://github.com/AutoHotkey/AutoHotkeyDocs/issues/615

white-ah
Posts: 8
Joined: 11 Jan 2023, 09:47

Re: [v2.0.2] Launcher doesn't handle #requires properly

Post by white-ah » 15 Jan 2023, 12:52

white-ah wrote:
14 Jan 2023, 13:33
  • #Requires v1
  • #Requires v2
I meant to say:
  • #Requires AutoHotkey v1
  • #Requires AutoHotkey v2

CoolCmd
Posts: 11
Joined: 13 Sep 2022, 06:37

Re: [v2.0.2] Launcher doesn't handle #requires properly

Post by CoolCmd » 29 Jan 2023, 15:21

white-ah wrote:
14 Jan 2023, 13:33
"v" before version number was always optional since introduction 1.1.33 but launcher assumes it is mandatory
yes, i was lost a hour or more due to this bug.



Post Reply

Return to “Bug Reports”