prino wrote: ↑28 Jun 2025 19:16
Nice, entered registration info and it ran. Not yet tried with the original ini-file, are they compatible?
But very important question, how long will you continue to support W7, now that the likes of the Document Foundation and GIMP have decided to terminate support for it?
For what it's worth, one initial crash after restart and "Help->About->Close", but then stable. Worrying thing is of course, not for me, that you will never own TwinBasic, unless you're one of the people who secured a VIP perpetual licence.
Inline assembler will be useful if you want to make it even faster, but what do will they support? Bog-standard run-of-the-mill code, or, which is probably an order of magnitude harder, things like AVX, which I myself use, unsupported, in Virtual Pascal, and which really works wonders.
It's currently fully compatible with the original INI file when reading it, but when writing it some 64-bit related keys are missing (in case you want to use this INI again with XYVB). But thinking about it, I will change this back to full two-way compatibility. I think it's useful for the VB->TB transition period.
Currently even XP support is still the Win version compatibility target. (With a few non-essential features excluded.) I don't see an end to W7 support for a long time.
"Help->About->Close": yes, crash after closing dialogs is a known issue. It will get eventually fixed, of course.
Why own? I worked so many years with a dead language I did not own. And I can stop upgrading TB whenever I want. There is no problem, only advantages.
Inline assembler: well, the bottle neck with a file manager is usually file I/O. And the TB version, once the compiler is optimized (which it currently isn't at all) will be much faster than the VB version anyway. So the need for inline assembler is small.