When did this change ?

[donkey]

Hi Jeremy,

I was just testing the compile time error messages of the Windows headers and found that there has been a rather fundamental change to GoAsm. When I use GOASM_ECHO or GOASM_EXIT in a header file it is ignored. As far as 0.56.5 it was working fine (the last archived version I have) however in 0.56.8 the conditional error messages in Windows.h are completely ignored. Though there are only 2 places where I use the messages I was hoping to expand the error reporting some day.

Edgar

[donkey]

Another issue with 0.56.8 is the error message encountered in the following post:

http://www.masm32.com/board/index.php?topic=13107.msg101711#msg101711

Error!
No code or data found in assembler source file
OBJ file not made

The error message indicates an empty asm file when it is not. I experimented a bit with the conditions under which it occurs and found this:

Code Select Expand

#DEFINE LINKFILES
#DEFINE WINVER NTDDI_VISTA

#IF WINVER < SOMEVAR
; Some directive here
#ENDIF

#include "Windows.h"
#include "macros.a"
#include "wbemcli.h"

Since SOMEVAR is not defined when it is compared to WINVER the rest of the file should normally be skipped, however in this case for whatever reason it is just skipping everything including the asm file and not giving the "Could not evaluate expression in conditional directive (rest of file skipped):-" message at all. The only message from GoAsm is the one I quoted above. This only occurs when the directive is in a separate header file, not in the asm file. Stopping the assembly here may not be a bad thing, it will prevent unexpected behavior in include files but I think the message should be a bit clearer.

Edgar