The information in this article applies to:
SYMPTOMSWith the Microsoft Macro Assembler (MASM), if the .NOLIST directive is the first statement in a file and it is later followed by a .LISTALL directive, then the macro expansion in the listing file will occur before the macro call instead of after it. RESOLUTIONThis problem can be eliminated by placing either a blank line or a comment before the .NOLIST directive, so that .NOLIST is not on the first line of the file. STATUSMicrosoft has confirmed this to be a problem in MASM version 6.0, 6.0a, 6.0b, 6.1, 6.1a, and 6.11. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
The .NOLIST directive prevents the macro expansion of all macro calls
in the listing file. This option shows the macro call, but it does not
display the corresponding code. The .NOLIST directive also prevents a
complete listing of every macro in each file that is included with the
.INCLUDE directive. The .LISTALL directive lists all source lines,
including false conditionals and generated code for each macro.
However, if .NOLIST is the first statement on the first line in the
file, then this order is reversed and the macro expansion appears
before the macro call. The incorrect macro expansion actually appears
as follows:
Sample CodeTEST.ASM
TEST.INC
Additional query words: 6.00 6.00a 6.00b 6.10 6.10a buglist6.00a buglist6.00b buglist6.10 buglist6.10a buglist6.11
Keywords : |
Last Reviewed: January 4, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |