Talk:Delay code: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
Rainwarrior (talk | contribs) (→Jxx pseudo-instructions?: seem to be orphaned at Fixed cycle delay) |
(explanation) |
||
Line 3: | Line 3: | ||
:Okay, I just found the definitions at [[Fixed cycle delay]] (left there by mistake?), which makes me understand that they're really just the straight branch with a page check. I think this is really bad nomenclature because of the already existing longbranch conventions which have the same names but different function. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 20:13, 16 March 2016 (MDT) | :Okay, I just found the definitions at [[Fixed cycle delay]] (left there by mistake?), which makes me understand that they're really just the straight branch with a page check. I think this is really bad nomenclature because of the already existing longbranch conventions which have the same names but different function. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 20:13, 16 March 2016 (MDT) | ||
::Sorry about the confusion. I'm not sure where I adopted these macros from. But that's what they do, branch with page-wrap check. The longbranch functions are named similarly, but with a lowercase j, not a capital J. --[[User:Bisqwit|Bisqwit]] ([[User talk:Bisqwit|talk]]) 22:22, 17 March 2016 (MDT) |
Revision as of 04:22, 18 March 2016
Jxx pseudo-instructions?
I'm noticing a bunch of branching pseudo-instructions starting with J instead of B. I presume this refers to an inverted branch across a JMP instruction, but given that this is tutorial material, shouldn't only real instructions be used? This code seems to be dependent on custom macros? ca65 does come with ".macpack longbranch", but they don't use a capital J as far as I understand, and ASM6 doesn't have anything of the sort packaged with it, does it? - Rainwarrior (talk) 19:43, 16 March 2016 (MDT)
- Okay, I just found the definitions at Fixed cycle delay (left there by mistake?), which makes me understand that they're really just the straight branch with a page check. I think this is really bad nomenclature because of the already existing longbranch conventions which have the same names but different function. - Rainwarrior (talk) 20:13, 16 March 2016 (MDT)