Ok,

Is there any way of getting rid of Phase errors when using macros? I'm assuming at this point its normal due to haveing to re-position addresses due to insertion of code, but I wasn't sure....

_________________
-Tony
KG4WFX

Macros of course have to be defined before they're called. No choice there, but it's no big deal. I did have a project once (10,000 lines? 15 years ago?) where the assembler's second pass gave a ton of phase errors IIRC but the third pass went perfectly. I can't remember now what the situation was, but I probably had a lot of conditional assembly in the macros. I'll come back and edit this if it comes to mind what it was. For now I'm just trying to think of what you might have that's producing errors. Whatever it was on that project, the screen looked awful to someone looking at it during assembly if they didn't know what was happening, but everything was fine with the extra pass.

What you said made me try something - the set8bit subroutine was originally in my LCD handler file, when I converted it to a macro, I left it in that file (of course, at the beginning of it instead of where it was) - I commented it out and placed it in what became the main file at the beginning and the phase errors went away. - thanks for the tip. I guess I assumed it would handle inserting the macro code during phase 1 before it generated addresses; no matter where the macro was - ie: it would scan the code for macros then go on to initial assembly...

_________________
-Tony
KG4WFX