SjASMPlus от z00m

[Ped7g]

https://github.com/z00m128/sjasmplus...es/tag/v1.14.3

v1.14.3 changelog:
- fix detection of `.end:` and `.END` labels when `--dirbol` is used
- added export of SLD (Source Level Debugging) data for NDS-NextDevSystem
- added `--longptr` option to allow labels outside of 16b address space
- docs: added small details about FPOS, SAVETAP, IFUSED
- fix assembling-time reported in linux

Documentation http://z00m128.github.io/sjasmplus/documentation.html (or in the package/cloned source).

The minor fixes and `--longptr` option are result of cooperation with "one abandoned project by Daemos" for MSX platform, who was trying to migrate from Tniasm to sjasmplus (now successfully migrated).

From the other feedback since v1.14.2... usually most of the issues turn out to be "lack of documentation" of sjasmplus specifics, when it doesn't meet expectations of user and it works in different way than they expect.

For example the (internal) distinction between modules+labels/macros/defines (all of them being different kind, and applied to the source line in different stage of assembling) is common source of confusion, as each feature is maybe too independent and having its own rules (how it works).

So I will try in future to add few more chapters to docs about how actually sjasmplus internally works and what are expected ways of usage.

If you have some issue on your own sources, if everything fails, don't hesitate to post some example here, or send me whole project so I can check the problem and suggest some workaround/fix. Obviously some of the reported issues would be nice to fix a bit more on the assembler side and less in the project source, but I don't want to change general behaviour of v1.14.x versions, adding only new features when they don't collide with old syntax and behaviour.

(the v1.14 series are sort of "final" versions of sjasmplus v1.x, and by the amount of new bugs found+fixed in recent releases I think I'm there already, with only minor fix releases coming in future... and then maybe later one day the v2.x will be released - which will have also behaviour and syntax changes, so I'm collecting also ideas for behaviour changes for the v2.x).