Wow nice job, there!lexikos wrote:... I went to considerable lengths to minimize the impact that these new features have on code size. The result is that this build is smaller than the previous one.
Obsolete test build - Functions and Objects as Labels (etc.)
Re: New test build - Functions and Objects as Labels (and m
Windows 10 x64 Professional, Intel i5-8500, NVIDIA GTX 1060 6GB, 2x16GB Kingston FURY Beast - DDR4 3200 MHz | [About Me] | [About the AHK Foundation] | [Courses on AutoHotkey]
[ASPDM - StdLib Distribution] | [Qonsole - Quake-like console emulator] | [LibCon - Autohotkey Console Library]
Re: New test build - Functions and Objects as Labels (and m
With every single new test build posted here, I feel more and more like the version number deserves bumping to v1.2 due to so many major changes to how AutoHotkey works.
fincs
Windows 11 Pro (Version 22H2) | AMD Ryzen 7 3700X with 32 GB of RAM | AutoHotkey v2.0.0 + v1.1.36.02
Get SciTE4AutoHotkey v3.1.0 -[My project list]
Windows 11 Pro (Version 22H2) | AMD Ryzen 7 3700X with 32 GB of RAM | AutoHotkey v2.0.0 + v1.1.36.02
Get SciTE4AutoHotkey v3.1.0 -
Re: New test build - Functions and Objects as Labels (and m
+1, language is evolving fast, i can't keep up. i'm surprised this stuff is even being considered for v1. personally would've preferred all of this to go into v2. just seems more fitting since v2 nudges users into using functions/expressions anyway.fincs wrote:With every single new test build posted here, I feel more and more like the version number deserves bumping to v1.2 due to so many major changes to how AutoHotkey works.
at one point i remember Lexikos saying that he wouldn't be doing much new dev work on v1 other than bug fixes, guess that's changed, which is completely fine and his prerogative
Re: New test build - Functions and Objects as Labels (and m
I had more or less "reserved" v1.2 for minor compatibility-breaking. I have also been entertaining the idea of forking the v2 code base to be closer to v1.x syntax, bringing the new features and many of the more minor compatibility-breaking changes to v1.x and making it easier to maintain. (But I probably won't do it.)
I don't see v2 being complete any time soon, but I want to actually use these features. This is also meant in part as a sort of stepping stone to v2. The further v2 diverges from v1, the harder it will be to get users to switch.
You could also say that all of this is for v2, I just happen to be developing it in the v1 branch. For example, %obj%() calls obj.() and therefore triggers __Call with an empty first parameter in v1, but in v2 it calls obj.call(). Hotkey, SetTimer, etc. in this test build use the equivalent of obj.call().
I don't see v2 being complete any time soon, but I want to actually use these features. This is also meant in part as a sort of stepping stone to v2. The further v2 diverges from v1, the harder it will be to get users to switch.
You could also say that all of this is for v2, I just happen to be developing it in the v1 branch. For example, %obj%() calls obj.() and therefore triggers __Call with an empty first parameter in v1, but in v2 it calls obj.call(). Hotkey, SetTimer, etc. in this test build use the equivalent of obj.call().
Re: New test build - Functions and Objects as Labels (and m
When test is released as main/stable, I concurr with fincs on the versioning To 1.2
Windows 10 x64 Professional, Intel i5-8500, NVIDIA GTX 1060 6GB, 2x16GB Kingston FURY Beast - DDR4 3200 MHz | [About Me] | [About the AHK Foundation] | [Courses on AutoHotkey]
[ASPDM - StdLib Distribution] | [Qonsole - Quake-like console emulator] | [LibCon - Autohotkey Console Library]
Re: New test build - Functions and Objects as Labels (and m
Another, more likely idea I have been entertaining is to bump the version number to v1.2 after back-porting a backward-compatible subset of v2 features. I've already done some work on Loop and some of the object methods.
Related topics:
Related topics:
Re: New test build - Functions and Objects as Labels (and m
in your mind, whats necessary to deem it "complete"? whats missing currently and are those necessary? why cant you just call it "complete" right now and then bump additions as v2.01 etc?lexikos wrote: I don't see v2 being complete any time soon, but I want to actually use these features. This is also meant in part as a sort of stepping stone to v2. The further v2 diverges from v1, the harder it will be to get users to switch.
just curious. i guess i'm more ansy than most to just get v2 out and become the main branch
Re: New test build - Functions and Objects as Labels (and m
I would kill for guicontrol and onmessage function binding in v2 right now.
I know the future of CHID and CGui lies with v2, but for now v1 test builds are just so much more convenient to code in.
I know the future of CHID and CGui lies with v2, but for now v1 test builds are just so much more convenient to code in.
Who is online
Users browsing this forum: No registered users and 9 guests