You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With option multilabel off, if I have label 0388 Obj_Laser_0 ; in my info file, then later on I get fdb Obj_Laser_0 20F4: 88 03 in my output file and it all assembles fine, because the label is declared earlier in the output file, i.e. Obj_Laser_0 equ $0388.
However, with option multilabel on, the above output code assembly fails because the label declaration is missed out, but only for fdb declarations (and probabaly fcb etc., I didn't test those instances). The rest of the labels are output and still assemble.
A workaround for this that does work is to use option multilabel on, which forces the label declaration, but this seems like it shouldn't be necessary.
I'm still not sure multilabel will solve my problem anyway 🙂
The text was updated successfully, but these errors were encountered:
With
option multilabel off
, if I havelabel 0388 Obj_Laser_0 ;
in my info file, then later on I getfdb Obj_Laser_0 20F4: 88 03
in my output file and it all assembles fine, because the label is declared earlier in the output file, i.e.Obj_Laser_0 equ $0388
.However, with
option multilabel on
, the above output code assembly fails because the label declaration is missed out, but only forfdb
declarations (and probabalyfcb
etc., I didn't test those instances). The rest of the labels are output and still assemble.A workaround for this that does work is to use
option multilabel on
, which forces the label declaration, but this seems like it shouldn't be necessary.I'm still not sure
multilabel
will solve my problem anyway 🙂The text was updated successfully, but these errors were encountered: