I want to know if masm 7.0 still has the 512 characters per line limitation.
japheth
japheth
AFAIK the 512 bytes / line 'bug' has been fixed quite a while ago. It doesn't seem to be in MASM 6.15 from M$s' Processor Pack.
thanks jmp $fce2,
I use 6.15.8803 from 16.3.2000 (was sure until now that the limitation still exists in that version)
japheth
I use 6.15.8803 from 16.3.2000 (was sure until now that the limitation still exists in that version)
japheth
@japheth
this gives a VERY nice & detailed overview how MASM has evolved over the years :
http://ourworld.compuserve.com/homepages/r_harvey/doc_book.htm
Quote :
"MASM 6.14: The Complete Assembler
...
The line-too-long bug is dead. The reason the problem was so hard to correct, I believe, was that it had nothing to do with long lines, but with the IF directive (I wish I'd mentioned that in 1992 when I reported the bug). Basically, instead of just saying "IF Something", always say "IF Something NE 0", and the error messages will go away. "
this gives a VERY nice & detailed overview how MASM has evolved over the years :
http://ourworld.compuserve.com/homepages/r_harvey/doc_book.htm
Quote :
"MASM 6.14: The Complete Assembler
...
The line-too-long bug is dead. The reason the problem was so hard to correct, I believe, was that it had nothing to do with long lines, but with the IF directive (I wish I'd mentioned that in 1992 when I reported the bug). Basically, instead of just saying "IF Something", always say "IF Something NE 0", and the error messages will go away. "
Just made a Test with masm 6.15:
Version 1:
assembles with no problems.
Version 2 (just 1 additional line):
assembles with error
DDTest.asm(36) : error A2041: string or text literal too long
So I must say in version 6.15 there still exists a very restrictive line limitation.
This limitation has nothing to do with the "line too long" bug and im afraid it still exists in masm 7.0
japheth
Version 1:
ThisIsAVeryLongProcedureName proc
ret
ThisIsAVeryLongProcedureName endp
.data
xxx IDirectDrawVtbl {ThisIsAVeryLongProcedureName, ThisIsAVeryLongProcedureName,\
ThisIsAVeryLongProcedureName, ThisIsAVeryLongProcedureName,\
ThisIsAVeryLongProcedureName, ThisIsAVeryLongProcedureName}
assembles with no problems.
Version 2 (just 1 additional line):
xxx IDirectDrawVtbl {ThisIsAVeryLongProcedureName, ThisIsAVeryLongProcedureName,\
ThisIsAVeryLongProcedureName, ThisIsAVeryLongProcedureName,\
ThisIsAVeryLongProcedureName, ThisIsAVeryLongProcedureName,\
ThisIsAVeryLongProcedureName, ThisIsAVeryLongProcedureName}
assembles with error
DDTest.asm(36) : error A2041: string or text literal too long
So I must say in version 6.15 there still exists a very restrictive line limitation.
This limitation has nothing to do with the "line too long" bug and im afraid it still exists in masm 7.0
japheth
Ok, so apparently you're right. DAMN !
I'll try to get hold of MASM 7.0 as quick as I can and see if it's still in there. OMG ! M$ morons didn't manage to fix this bug within YEARS :mad:
I'll try to get hold of MASM 7.0 as quick as I can and see if it's still in there. OMG ! M$ morons didn't manage to fix this bug within YEARS :mad:
Microsoft (R) Macro Assembler Version 7.00.9254
Copyright (C) Microsoft Corporation. All rights reserved.
Assembling: Indices.asm
Indices.asm(235) : error A2041: string or text literal too long
Make error(s) occured.
This is very disappointing, as it is the single limiting factor in my macro development.