JWasm new version v1.96

[BogdanOntanu]

I tweaked the format of JWasm's error messages a bit: added "severity" to the error number, so 1xxx are fatal errors, 2xxx are errors and 4xxx are warnings, and also replaced the prefix 'E' or 'W' by 'A'. If RadASM still isn't satisfied, I probably can't help.

One simple solution would be to mimic exactly the MASM's error messages line layout. This way RadASM will parse them just like it does for MASM now.

Alternatively you can use your own layout but keep in mind that  RadASM will parse the assembler's output seeking for:
1) An error marker token probably "**Error" or something
2) The source file name where the error is located
3) The line number where the error is located

It is pretty easy to change the error printf format to match RADASM's requirements and in exchange you obtain a huge advantage: the IDE will automatically open the source file and highlight the error line for the user.

The error number and it's hexadecimal subfields are not parsed by RADASM.

I did this for Sol_ASM and IMHO it is easy to be done for any assembler.

The times when you used makefiles and manually seek for errors after the compile's console output are long gone. Today the ASM IDE's  highlight error lines, help code browse, collapse code, type for you, suggest parameters, show EQU's by mouse hover,  etc. Using an assembler without the help of an advanced IDE is an unnecessary torture.

[Ficko]

Hi Bogdan!

I did this for Sol_ASM...

Do this means that you may have a "Sol.ini" sandbagged - not published in the "RadASM programming pack" - for highlighting and parsing too ? :toothy

Or I just reading too much out of your lines?

[BogdanOntanu]

Hi Bogdan!
...
Do this means that you may have a "Sol.ini" sandbagged - not published in the "RadASM programming pack" - for highlighting and parsing too ? :toothy

Or I just reading too much out of your lines?

Hi Ficko,

Yes that is correct. I do use RadASM with Sol_Asm and yes "sol_asm.ini" and additional API files do exist but are not yet published in RadAsm programming pack. I did handcrafted them by reading the RadASM manuals comparing with other .ini files (MASM/TASM) and by asking Ketilo some dumb questions :D  ... Maybe I should release them...

Although initially HE RTS was written in "plain" text editors today I would not dare to handle big ASM projects without an advanced ASM IDE like RadASM. Code browsing is a lot of fun.

Hence I think that JWASM should also benefit from those "pleasures" of using an advanced ASM IDE.

[Ficko]

... Maybe I should release them...

Are you joking? :dazzled:

Yes, you should!! :clap:

The main reason I am not doing too much with Sol_asm because I went B/W-blind from RadASM. :bg

[Farabi]

 :U
Hi japhet, nice to see you still here.
Im a big fans of RadAsm. It would be great if you follow bogdan sugestion. Or maybe, I will try another IDE.
JWASM is my ultimate weapon in case Im move to linux. Ubuntu getting very popular among my other community.

[japheth]

Hi Farabi,

Im a big fans of RadAsm. It would be great if you follow bogdan sugestion. Or maybe, I will try another IDE.
JWASM is my ultimate weapon in case Im move to linux. Ubuntu getting very popular among my other community.

But there is almost certainly nothing to do from my side anymore. Some days ago I posted:

I tweaked the format of JWasm's error messages a bit: added "severity" to the error number, so 1xxx are fatal errors, 2xxx are errors and 4xxx are warnings, and also replaced the prefix 'E' or 'W' by 'A'. If RadASM still isn't satisfied, I probably can't help.

So please test JWasm v2.0 if it does this "highlighting thing" now! JWasm v1.96 is final and won't be changed anymore.

[Ficko]

Thanks Japheth!

It does work now !! :U

[Ficko]

But there is an other problem. :(

I am getting

Error A2054: Invalid instruction operands

by

Code Select Expand


movq mm0, qword ptr [l1]

JWASM200B
but

Code Select Expand


movq mm0, dword ptr [l1]


seems to be ok.

JWASM196B
Takes it just fine.

Using

Code Select Expand


.686p
.model flat
.mmx


flags

/Zg -zlf /c /coff /Cp /nologo

[japheth]

But there is an other problem. :(

I am getting

Code Select Expand


Error A2054: Invalid instruction operands


Well, I guess that's why it's called unstable. This error might be fixed now, but please don't use the current development version for anything serious!