You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably to be done first in macros as proof of concept (and maybe stay like it as I expect little of added value by integrating them into sjasmplus binary, the performance boost is not important for these small files, but the flexibility of adjusting macros over fixing sjasmplus binary may be better value, even with the inconvenience of having to include the macro definitions file.
TODO:
few example .o/.p files (end result) with some suggestion how the source code producing those may look like (NOT @ped7g )
filling up any gaps in the .o/.p defs like what sysvars should be pre-filled by sjasmplus, if any
implementing proof of concept macros ( @ped7g probably)
Is surely not optimized but might be used for the "Hello World" purpose
Compiled with "./sjasmplus --outprefix=. --sld helloworld.asm --lst=helloworld.lst --raw=helloworld.p" and tested ok on zesarux
Let me add that for a "real program" experienced programmers would use - expecially for the 1k version - more "condensed" ways of loading and starting the assembler and depending on the type of program to be implemented
Out of scope for 1.21.0, will take a look at some point after that. So I guess this is like months/year away with my current progress rate. But eventually this is likely to happen.
as mentioned in #232 the virtual device "NOSLOT64K" is good enough, but having support for .p files would be also nice.
file formats description: https://k1.spdns.de/Develop/Projects/zasm/Info/O80%20and%20P81%20Format.txt
Probably to be done first in macros as proof of concept (and maybe stay like it as I expect little of added value by integrating them into sjasmplus binary, the performance boost is not important for these small files, but the flexibility of adjusting macros over fixing sjasmplus binary may be better value, even with the inconvenience of having to include the macro definitions file.
TODO:
possible contributors to get this going: @maziac @stevexyz
The text was updated successfully, but these errors were encountered: