x86 Assembler JWASM Hits Stable Release
Odoital writes "January 2010 is an exciting month for x86 assembly language developers. Software developer Andreas Grech, better known to the x86 assembly language community and the rest of the world by his handle "japheth," has released another version of JWASM — a steadily growing fork of the Open Watcom (WASM) assembler. The main benefit of JWASM, arguably, is the nearly full support of Microsoft's Macro Assembler (MASM) syntax. As those in the assembly language community may already know, Microsoft's desire to continually support the development of MASM has been dwindling over the years — if only measurable by a decreasing lack of interest, updates and bug fixes — and thus the future of MASM remains uncertain. While Intel-style syntax x86 assemblers such as NASM have been around for a while, JWASM opens up a new possibility to those familiar with MASM-style syntax to develop in the domains (i.e. other than Windows) in which assemblers such as NASM currently thrive. JWASM is a welcomed tool that supplements the entire x86 assembly language community and will hopefully, in time, generate new low-level interests and solutions."
We have Java!
Deleted
January 2010 is an exciting month for x86 assembly language developers.
I'm sure the two of them will be pleased.
Japheth has a number of rather interesting projects that extend the functionality of DOS.
Awesome, I'm always on the lookout for cool stuff like this to keep my DOS workstation cutting edge.
sic transit gloria mundi
joel does all his work in vb. Not vb.net, vb. His endorsement is kind of useless.
Let's write some nVidia drivers in Java!
Weaselmancer
rediculous.
And then I get to watch the color drain from your face when I tell you that:
xor ax, ax
cwd
xor ax,dx
sub ax,dx
results in zero, and that your code is relying on a non-zero value in the AX register in order to do anything useful.
You don't need the pusha/popa OR the NOP. And you forgot to load dx with the message offset! No soup for you!