Hey, this actually doesn't work.

[$nooc]

thank you guys for your explanations :)

[MrBogus]

print is a macro defined in macros.asm :

Code Select Expand

    print MACRO arg1:REQ,varname:VARARG      ;; display zero terminated string
        invoke StdOut,reparg(arg1)
      IFNB <varname>
        invoke StdOut,chr$(varname)
      ENDIF
    ENDM


chr$ is another macro defining NULL terminated strings in the data section :

Code Select Expand


chr$ MACRO any_text:VARARG
        LOCAL txtname
        .data
          txtname db any_text,0
        .code
        EXITM <OFFSET txtname>
      ENDM

Where does StdOut came from? I've seached its declaration in macro.asm file but I haven't found any.
Just wanted to learn how print macro really works. Thanks.

[Vortex]

StdOut.asm can be found here :

Code Select Expand

\masm32\m32lib\stdout.asm

[MrBogus]

Thanks for the quick reply. But why is it that there is no statement such as this

Code Select Expand


include \masm32\m32lib\stdout.asm


in macros.inc file?

[MichaelW]

For MASM32 there is no macros.inc file - most of the MASM32 macros are in the file masm32\macros\macros.asm. Placing the statement:

include \masm32\m32lib\stdout.asm

In macros.asm would effectively include the source file in macros.asm, and this would cause multiple problems building any source that included macros.asm, starting with multiple model directives and duplicated include files. The source file stdout.asm, like the other source files for the MASM32 library, is structured so it can be assembled and linked into the library masm32.lib. A source can use the MASM32 library procedures by including masm32.lib and masm32.inc, along with the include files and libraries that the MASM32 library depends on, and the source can then call any of the macros in macros.asm without problems.