SjASMPlus от z00m

[Ped7g]

Can you please restore support for backslash-escaped characters in single-quoted character constants? Rationale: it was supported in v1.07, and it's used in NedoLang output (it exports constants directly from *.c).

hmmm... maybe as extra --syntax option, but not sure if/when...

I have a suspicion it's a bit more difficult than it may seem ... although maybe if I would treat apostrophe the same way as quote, it would work as long as you will not try to break it ... i.e. 'don\'t do it' would parser see as "don\'t do it", which would work, but then <apostrophe><quote><apostrophe> would be invalid (would need <apostrophe><backslash><quote><apostrophe> to work), and 'text" would become valid (!)... if such hack is enough for you, maybe it will happen. But to do it properly would basically need two versions of buffered-reader and line parser code, as both are hardcoded to parse strings as defined in the documentation. Basically I'm not a big fan of this idea.

Also I see, support for UTF8-encoded sources was dropped, so it shows an error at the beginning BOM marker. Can you please restore it? There was a bug previously: BOM marker should be followed by a blank line.

I don't recall it was even there, but maybe it worked due to some quirk... definitely good idea, I will make a note to my TODO. But you can also just strip the BOM marker out of the file... I have to do that pretty often in our commercial Android projects.... I think in some projects I have even some batch shell script to scan all the files and cut it out where it's found. I think in linux world BOM marker is not that important, not sure about elsewhere. (that's like "workaround" suggestion, I will try to fix BOM parsing in future)

One more question: is it possible to remove the following messages in the output:
Pass 1 complete (0 errors) ...

--msg=none|war|err

And make error lines RED? That's crucial because there are so many programs in the project.

hmm... maybe... but if you are building from IDE/text editor, they usually do it for you, like for example this is how it looks on my machine in Kate:



... so, depends what you are using, also if you are using command line, then you can also catch output into file and open it in text editor...
This is also small asnwer for NEO SPECTRUMAN, if I understand his problem correctly? ("Ped7g, а еще в целях отладки не хватает pause")

you can do `sjasmplus --some-options file.asm 2> error.log.txt` and open that in the text editor, then you can use Search all to highlight Error lines... (but warnings/errors are now channelled to STDERR, not STDOUT, so you must redirect with "2>", not simple ">" or "1>")

- - - Updated - - -

But I'm glad you find sjasmplus useful... hopefully some of these will make it even more useful... I'm kinda really unhappy about that apostrophe thing, sjasmplus had this syntax defined long time ago, I just fixed the parsers, it was not my idea. And for assembler purposes the "no escaping" is often helpful, while in C/C++ I think the escape-always makes more sense. ... I would like lot more if you would fix your output instead to produce "correct" asm source..