18 Jan
2006
18 Jan
'06
7:26 p.m.
On 1/18/2006 at 7:06 PM Fred Cisin wrote:
Phase errors were usually caused by forward
references,
MOV VAR2, 0
. . .
VAR2 DB ?
and would then generate the message for EVERY label from there to the end.
Avoiding forward references, or overiding the datat type would prevent
them MOV BYTE PTR VAR2, 0
That would be too easy! MASM 1.0 would generate phase errors for seemingly
no paricular reason. Sometimes, just rearranging the order of instructions
(without changing the nature of the references would clear them up. As I
said, a miserable excuse for a product.
Cheers,
Chuck
MASM 4.0 was like a breath of fresh air.
Reasonably fast and not too
buggy.
... and 5.0 was the first one with tolerable documentation provided.