Re: [Clax86list] using common macros in NASM and C

On 26 Jul 2006 09:24:07 -0700
"randyhyde@xxxxxxxxxxxxx" <spamtrap@xxxxxxxxxx> wrote:

:Are we not talking about macro definitions in this thread?

Not seeing any value in discussing the definition of a macro, let me
merely state that my usage of the term is consistent with the definition
found on Whatis.com, "A macro is a programming language statement that,
when processed, generates a sequence of more detailed language statements."

:It is *very* rare for a typical C header file to translate easily to
:assembly language.

This has not been my experience, which, as you know, is somewhat greater
than yours.

:For example, don't try this
:with most of the Windows header files and try to create a NASM
:equivalent.

For reasons which have nothing to do with this thread, I have no intention
of converting any Windows header files. However, I have converted portions
of several Linux header files to both NASM and FASM, and the results are
available on my web site, for all to see.

-- Chuck

.

Relevant Pages

  • Re: [Clax86list] using common macros in NASM and C
    ... Not seeing any value in discussing the definition of a macro, ... generates a sequence of more detailed language statements." ... :with most of the Windows header files and try to create a NASM ... However, I have converted portions ...
    (comp.lang.asm.x86)
  • Re: what will be the value of #define
    ... convention for ensuring that multiple inclusions of header files ... #ifndef FRED_H ... then the first inclusion will have the macro "FRED_H" undefined, ...
    (comp.lang.c)
  • Re: what will be the value of #define
    ... #ifndef SYSTEM_H ... defined as an object-like macro whose replacement list is empty. ... convention for ensuring that multiple inclusions of header files ... But there's no reason to care what it expands to, ...
    (comp.lang.c)
  • Re: what will be the value of #define
    ... #ifndef SYSTEM_H ... defined as an object-like macro whose replacement list is empty. ... convention for ensuring that multiple inclusions of header files ... define the macro (as an empty macro) and do the other declarations, ...
    (comp.lang.c)
  • Re: A "killer" macro
    ... could be included as a feature in another language, ... The "killer" macro, in CL ... of the functional features of Lisp. ... When confronted by fellow programmers with the question "so why is ...
    (comp.lang.lisp)