Re: Question about jumps


Frank Kotler wrote:
Evenbit wrote:

...
; nasm -f elf -l stk2.lst -Xvc -O8 -o stk2.o stk2.asm

Odd combination of switches... Is there a reason you're asking for
VC-style error messages, or is that just carried over from what you use
in Windows?


No, it isn't a hold-over, just a perversion. I can spot the line
numbers just fine using the default reporting. However, the format
seems to be designed for machine-reading (as in an IDE parses it), so I
selected the Xvc form because it 'looks' like it is meant to be human
digestible. ;)

The -l is vestigial -- because I am accustomed to having the results of
HLA's hindquarters available if I need to verify that things are being
assembled the way I think they should be. The -O is left-overs from an
earlier brain-fart. NASM was vomitting at some multiple-parameter
nested macros I had cooked. BURURURURR! Wrong! That was one of the
most nucking futty ideas I've ever dreamed up. [note to self:
pre-processor directives are there for a *reason*, Nathan, *use them*!]
;)

On that note, it occurs to me that if one were to continue to build up
a nice "cut-and-paste" style 'library' of code (as I've suggested in
this thread), they would eventually want to move it to a more
maintainable static library + include file collection. The "asmutils"
package is ripe with resources to that end. Probably would want to
scale it down a good bit to make a "Linux NASM Beginner Kit" package.
But if one's goal is "Any *NIX (including BSD) Standard Library", then
the "asmutils" includes seem to provide that portability. There is no
mention of OS X, so I wonder if anyone has tried to build this package
there?

Nathan.

.