SjASMPlus от z00m

[Ped7g]

Unfortunately the "syntax=i" does exist because it was reasonably easy to add to current code.

The planned "I" for labels, and making the "i" or "I" affect also macros and defines is surprisingly high-friction in current sjasmplus.

I will take a look again, what is the exact problem, but it did look to me it's lot less problematic to fix the asm source to use correct case, than add case insensitivity to labels/macros. But maybe I just didn't find the simple solution.

"endX" vs "eX" - I agree with your idea, to bring better consistency into the "language", but code written for sjasmplus already does use current keywords, and just adding dozen new keywords for future will maybe break someone source (if they use the keyword as label or macro name), and will make even bigger mess.

I think I will keep this as compatibility-breaking change for v2.x, if it ever happens (cleaning up the directives keyword, maybe even removing some duplicities like rept vs dup, and similar), as the v2.x will be presented as not 100% compatible (there will be more syntax changes, not big, but enough to break old sources).

But I have still no idea when v2.x will happen, currently I have no time and no energy/incentive to work on it, the v1.x is quite OK currently. I don't like everything about it, but I can live with the current version.

The "$$$" is the only simple thing to add, which also looks like it would not break anything, but if I will add it, I think I would prefer the GCC-ification of it, i.e. __LINE__, __FILE__, etc... to copy the standard C/C++ macros when possible. I'm pretty sure I even have __LINE__ somewhere in my notes for v2.x.

... so, thanks for ideas, it's increasing priority of some things I have in plans, but I don't have any particular date when these things will happen.

-------------------
Meanwhile the next version will be v1.15.0, the planned changes so far:

- reworking the virtual device state for zx48/zx128+ to make the virtual memory closer to the fake "CLEAR x : LOAD "" CODE : RANDOMIZE USR y" state, which will change SAVESNA snapshot binaries (will hopefully break only minimum of projects, but fix the few issues I have seen recently, like the ROM keyboard routine reading BASIC keywords instead of characters, or the examples/Fros4k intro was broken in v1.13.0..v1.14.4 because the snapshot stack was $FFxx, in older versions it was $6000 ... after new changes it will be around $5D00 or something like that (impossibly low fake CLEAR).

- hopefully the larger memory spectrum-like devices, if I don't forget about it again

- maybe removing few more VS-specific calls and using the same source under every compiler

... I was hoping to release v1.15.0 around end of Feb initially, but currently I have no time to develop sjasmplus, so maybe toward end of March or April.
(and I will check again, if there's some simple trick for case insensitive macros, but I can't promise anything, last time the code did look very fragile and difficult to modify without affecting the assembling speed a lot)

BTW, about assembling speed... I was for fun trying out older versions, and seems the v1.14.5 is about two times slower than 1.10.4 ... Then again I personally prefer +0.2s per assembling instead of +100 bugs in assembler...

[Advertiser]