Using masm32 - latest one I think.
EX: getout:
This is the way I had it coded for months in a working program.
Today I got error A2006. Complaining about scope I think.
Anyway I put two ::s after it and the error went away. :eek
This is not the assembler I know.
Also in the same program "createwindowsex" code that has been working
for the same amount of time is causing trouble.
Yes I have ESET SS 5 and it is up to date. Also Malwarebytes and it is up to date,
also Sweepi. None of these show any viruses.
Only thing I suspect is the new HIPs in ESET which I know absolutely nothing about.
Any ideas would be most welcome....
code, ml&link commandline?
From my knowledge Sr shankle, if you define a label using only one ":" you are instructing the assembler to treat that label as LOCAL inside some PROCedure where it appears.
If you put "::" , now that label is global by the module.
.386
.model flat,stdcall ;C
.code
Main proc
jmp that
return: ;here is your question, change it with 2 "::"
;if not,"error A2006: undefined symbol : return"
ret
Main endp
that:
jmp return
end Main
yes, 2 colons makes a private label public :P
however, that does not explain why Jack experienced the change
perhaps he altered the OPTION CaseMap directive ?
or, as qWord mentioned, the command line
Thanks guys for the reply.
No Dave I did not change that instruction.
It's working again so I am happy.
Strange.
Ancient Shankle