Re: Two Click disassembly/reassembly

Evenbit wrote:

program bottles;
.... 
Well, I did see *my* version gain enough votes on that site to get
ranked in second place on that site one day.... but that doesn't mean
anything.

Better'n third place! There's a lot of competition on that site. My goodness, there are a lot of languages!

Might be interesting to read any comments if yours and
Randy's versions were to be posted there as alternatives.  I can "proxy
submit" them if you two don't mind and can give the attribution as
"found on the 'net" or "version suggested by ..." if either of you have
an issue with your names appearing on a website (which your minister's
wife can access) directly associated with the word "beer"?

I've got no problem with it either way - mostly *your* code! I suspect the way I allocated a buffer could be done in a more "hla-like" way. I tried several permutations of "string", but anything I could get hla to swallow segfaulted...

static
	english_number :byte[128];
....
	conv.utoEng( ecx, &english_number );
....

Seems to work okay, but there's probably a "nicer" way to do it. If it's going up as an "example", it ought to be "nice".

I may be screwing something up here, but I suspect there's something
"funny" going on with hla's macro-processing in Linux. If anyone else is
getting these to work, it's "just me"...


I am not able to try it on Linux at the moment.  But I am confident
that you are correct in pointing the finger at HLA's macro-processing.
The issue is not limited to Linux.  If you can recall a time many blue
moons ago (or craw amoung the cobwebs in ALA's dark cave repository)
when Randy suggested an Object-Oriented Syntax and provided some macro
code to test the concept with; I took the liberty of extending the
code.  When my code failed to compile, Randy said something about
mumble bugs with multiple macro definitions mumble mumble jerry-rigged
mumble Flex/Bison mumble.  Said he wouldn't fix it because it would be
easier to impliment proper macro processing in the HLA 2.0 release than
to further mumble jerry-rig mumble current 1.x prototype.  He told me
to occasionally insert abitrary constants in-between multiple macro
definitions as a temporary work-around while we all wait for the HLA
2.0 product.  I tried the work-a-round [see "xoos.hhf" in the FILES
section] but it still will not compile.  This is why I never use macros
when writing HLA code.

Thank you for the testimonial to hla's macro power. So powerful, only Randy can run it! :) Seriously, that's why there's a prototype. These issues will work themselves out.

But don't put Randy's code on the "99 Bottles" site until he gets it right! That's the first rule of assembly homework, as I understand it, "must assemble". :)

Best,
Frank
.

Relevant Pages

  • Re: Two Click disassembly/reassembly
    ... > when Randy suggested an Object-Oriented Syntax and provided some macro ... When my code failed to compile, ... > mumble bugs with multiple macro definitions mumble mumble jerry-rigged ... > definitions as a temporary work-around while we all wait for the HLA ...
    (alt.lang.asm)
  • Re: Two Click disassembly/reassembly
    ... when Randy suggested an Object-Oriented Syntax and provided some macro ... mumble bugs with multiple macro definitions mumble mumble jerry-rigged ... to further mumble jerry-rig mumble current 1.x prototype. ... definitions as a temporary work-around while we all wait for the HLA ...
    (alt.lang.asm)
  • Re: Two Click disassembly/reassembly
    ... > mumble bugs with multiple macro definitions mumble mumble jerry-rigged ... > to further mumble jerry-rig mumble current 1.x prototype. ...
    (alt.lang.asm)