Skip to content

Conversation

@TC01
Copy link

@TC01 TC01 commented Feb 22, 2014

I already posted about this on the bug report: since no one has responded there I figured I'd open a pull request.

This should prevent undefined labels from being silently ignored and replaced with a jump to 0x1234. All it does is make the assembler return an error when an undefined label is encountered instead of pretending everything was successful.

If I had to guess, I'd say 0x1234 is being pushed so it can be detected later from elsewhere. However, the code to actually do this doesn't seem to ever have been implemented, so this is better than nothing.

… false when detecting undefined labels in checkAbsolute* functions
@BigEd
Copy link
Collaborator

BigEd commented Feb 27, 2014

I think the idea of 0x1234 is to be a placeholder for forward references, so the code comes out the right size and labels are in the right place on the second pass. Can you confirm that your fix works with code that has a forward reference? Do all the example easy6502 programs still work?

@TC01
Copy link
Author

TC01 commented Mar 6, 2014

All the example programs with labels from here still compile and run: http://skilldrick.github.io/easy6502/

I thought that it might be for something like that as well; however a quick search through the source code didn't turn up any other occurrences of 0x1234. So if it is meant to do something like that, I'm not entirely sure how it is doing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants