Talk:Delay code: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
(explanation) |
m (Reverted edits by 69.20.131.234 (talk) to last revision by Tepples) |
||
(10 intermediate revisions by 6 users not shown) | |||
Line 5: | Line 5: | ||
::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) | ::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) | ||
:::Would bccnw, beqnw, etc. describe the intent better? --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 16:55, 20 March 2016 (MDT) | |||
::::Maybe. Should I change it? --[[User:Bisqwit|Bisqwit]] ([[User talk:Bisqwit|talk]]) 12:35, 21 March 2016 (MDT) | |||
:::::I think it would be a good idea to change them, yes. I don't have much opinion about what to use ("nw" seems as good as many), just I don't like the current similarity to the longbranch macros. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 12:23, 24 March 2016 (MDT) |
Latest revision as of 22:39, 9 April 2017
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)
- 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. --Bisqwit (talk) 22:22, 17 March 2016 (MDT)
- Would bccnw, beqnw, etc. describe the intent better? --Tepples (talk) 16:55, 20 March 2016 (MDT)
- Maybe. Should I change it? --Bisqwit (talk) 12:35, 21 March 2016 (MDT)
- I think it would be a good idea to change them, yes. I don't have much opinion about what to use ("nw" seems as good as many), just I don't like the current similarity to the longbranch macros. - Rainwarrior (talk) 12:23, 24 March 2016 (MDT)
- Maybe. Should I change it? --Bisqwit (talk) 12:35, 21 March 2016 (MDT)
- Would bccnw, beqnw, etc. describe the intent better? --Tepples (talk) 16:55, 20 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. --Bisqwit (talk) 22:22, 17 March 2016 (MDT)