Michael Devore wrote:
...
Okay, that was painful. The ATAPICD assembly code is already a we1ird
amalgam of NASM and MASM/TASM code. Plus it appears to improperly use
I agree it is painful
EQUates globally that can be IFDEF'ed out of sight, and has a few other
quirks.
:-) how do you improperly use an EQU? (-:
But seriously, any suggestions to improve it (both in function or style)
are welcome. In may latest versions (0.5.x) I've gone back to just
MASM/TASM form (I can't stand NASM's positional based macro parameter
names, FASM had no list support, and I couldn't get my segments to link
in the proper order for a mostly C version using OW).
But with the addition of pre-processing regular expression option
support in Nomsyo (to match the post-processing option added for FreeDOS
HELP), and a bit of hand massaging, I was able to get a clean NASM
assemble on a translated version of the ATACPICDD.ASM source. Clean
without turning on all the optional assemblies, anyway.
...
out of curiosity which version of atapicdd did you run this on? and did
you do it on the TASM source (atapicdd.asm) or NASM source (atapicdd.nsm)?
I suppose one of these days I'll run it on the source myself as I'm
curious what the generated NASM source looks like, especially in
comparison to the fully (not hybrid) NASM and MASM sources.
Jeremy
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
