Re: HLA Paren Rules


Eman wrote:

"One-to-one" is somewhat troublesome and maximalistic expression,
but we should be smart enough to understand the point. Actually,
macros do not violate "total control" principle because they are
under developer' control. In contrast to "intrinsic" "niceties".

So what is the difference between a macro of the form "if( eax=ebx)"
and a statement of the same form provided by the assembler? From the
user of that statement, none whatsoever at all.


Then you have synonyms, like JB and JC or NOP and XCHG eax, eax
where two instructions map to the same exact machine code. Again, the
one-to-one correspondance is broken.

?

JB and JC are the exact same instruction. They both map to the same
exact opcodes (there are two opcodes for these two instructions; so you
actually have a two-to-two mapping here).


Various ways to translate an asm instruction into machine codes do not
matter since they comply with requirements of Intel specification.

But the Intel specification doesn't support the notion of a "one-to-one
mapping". Hence my point.

Flags
affected, registers' changes, and possible exceptions etc are significant.

???


Today, modern programmer would not ever consider using an assembler as
the only game in town. Asm knowledge is necessary for debugging and reverse
engineering (if your local statute permits that). But as the primary
programming tool it is expedient for special tasks only.

But if they're going to use assembly language, they're probably going
to use a decent assembler, no?

Cheers,
Randy Hyde

.

Relevant Pages

  • Re: RosAsm?
    ... not what the instructions are. ... With a good set of macros this can be made even clearer... ... in this vain in my option the only programmers who should be ... by the assembler in a "Label not defined" error and probably ...
    (alt.lang.asm)
  • Re: ASM vs HLL : absurd war
    ... > I see it as anything that allows you to program in instructions that are ... Or JIT compilers. ... > Such things as Macros and HLA do muddy the waters somewhat, ... I'd say an assembler without a macro facility isn't really that useful. ...
    (alt.lang.asm)
  • Re: Evolution
    ... The idea that an assembler should do nothing ... >> combinations of libraries that I write myself and macros that I write ... > or two instructions if you ... this is the main reason to learn assembly programming. ...
    (alt.lang.asm)
  • Re: Hey, what is all this off topic posting?
    ... > things) I had a set of x86 assmebler macros that would do PL/I-like ... structures yet again using compare and branch instructions (or write the ... macros using some arcane assembler to do that on a new architecture), ... C was designed to be a portable assembly language, and, in my ...
    (sci.electronics.design)
  • Re: Evolution
    ... > inline assembler and larger parts by linking to an assembler ... in the HLL. ... language, particularly in smaller projects. ... > or two instructions if you ...
    (alt.lang.asm)
Loading