-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
assemble error with macro - inline maths?? #87
Comments
Looks like a bug, probably due to changed token handling after 1.4. |
Please try to build from the latest master branch to see if this indeed fixes the issue |
Latest commit adds the possibility to have argument names that partly overlap, like 'arg', 'arg1' and 'argument', while still expanding them correctly in the macro. |
Very quick build before bed, but I think that has done it!!! thank you. I will test further tomorrow. Build script for AgonLight2
|
Fixed in release v1.10 |
I am revisiting my Lunar Lander game, try to improve some of the motion.
Before making any changes to my previous master sources, I tested assembling on the latest ez80asm, but it failed.
In version 1.4, this assembles fine. But, with 1.9, it gives an error.
I haven't tested with any intermediate releases as I hadn't used any on my Mac.
As we have seen before, it may not be anything to do with this line at all!!
I am building a string of data to send to VDP with some macros.
eg.
MAKEBUFFEREDBITMAP 20, 320, 120, "resources/lunar_title.pbm", titleColour
(titleColour is an EQU)
Where the macro starts with:
It gives assemble error of:
Pass 1...
Pass 2...
�[31mMacro [MAKEBUFFEREDBITMAP] in "macros.inc" line 307 - Unknown label, invalid number�[33m 'bitmap_id'
�[39m�[33m .dw 64000 + bitmap_id
�[39m�[31mInvoked from "lander_29.asm" line 1732 as
�[33m MAKEBUFFEREDBITMAP 20, 320, 120, "resources/lunar_title.pbm", titleColour
If I step through each line in the macro and remove any of the maths (+ *, /, etc) it no longer reports an error for that line.
So, is there an issue doing basic maths within a macro now??
The text was updated successfully, but these errors were encountered: