The information in this article applies to:
SYMPTOMS
The Microsoft Macro Assembler (MASM) version 6.0 will incorrectly parse a
comment as if it were a conditional-assembly directive if the following
conditions are met:
CAUSEWhen both of these conditions are true, the conditional-assembly directive is given precedence over the comment block. The conditional directive is treated as a keyword although it was not meant to be treated as such. RESOLUTIONTo work around the problem, make sure that the first word on the line inside the comment block is not the same as a conditional directive. For example, in the sample code, one solution is to change the line "If should be ignored in a comment" to "An if should be ignored in a comment." STATUSMicrosoft has confirmed this to be a problem in MASM version 6.0. This problem was corrected in MASM version 6.0a. MORE INFORMATIONIf the conditional-assembly directive is either IF, IFE, IFB, IFNB, IFDEF, IFNDEF, IFIDN, or IFDIF and there is no associated ENDIF at the beginning of another line, then the following errors will be generated: If the conditional-assembly directive is ELSE, then the following error is generated: If the conditional-assembly directive is ELSEIF, then the following errors are generated: If the conditional-assembly directive is ENDIF, then the following errors are generated where the invalid character referred to is the closing delimiter. The sample code below illustrates this problem. It meets the above conditions, so it is parsed incorrectly and the following errors are generated:
Sample Code
Additional query words: 6.00 buglist6.00 fixlist6.00a
Keywords : |
Last Reviewed: January 13, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |