add explanations for remaining coincidental similarities

This commit is contained in:
Paul Gardner-Stephen committed 2019-05-07 12:40:41 +09:30
1 parent 61b69ddf3d
commit 0f18e18e9b
21 files changed
+87 -4

No files matched your search

+4
View File
@@ -0,0 +1,4 @@
fragment + TYA + STA ($nn),Y
simple register manipulation and store to contents of pointer.
Not creative, not copyrightable.
+3 -1
View File
@@ -1 +1,3 @@
Instruction fragment + store A in ZP. Single instruction. Not copyrightable.
instruction fragment followed by increment of ZP location.
Single instruction. Not copyrightable.
+4
View File
@@ -0,0 +1,4 @@
Fragment + Load X from memory location.
Only one whole instruction. Not copyrightable.
Not creative.
+5
View File
@@ -0,0 +1,5 @@
JSR $E544 (clear screen) surrounded by fragments
Single instruction calling well-known and documented routine
(Compute's Mapping the 64 p215).
Not creative. Not copyrightable.
+6
View File
@@ -0,0 +1,6 @@
set a bit in $DD00, Return from subroutine, read $DD00
$DD00 is a key IO register for the IEC serial port.
Thus it is no surprise to find routines that manipulate $DD00,
and indeed for them to appear one after the other.
Nothing creative. Not copyrightable.
+9
View File
@@ -0,0 +1,9 @@
Or A with $30 and print result
Printing digits from hex nybls requires adding the base
value for the digit 0 to the value.
As an example, we can see this sequence for the BBC micro here:
http://beebwiki.mdfs.net/Number_output_in_6502_machine_code
Not creative. Not copyrightable.
+5
View File
@@ -0,0 +1,5 @@
CLC / CLI / RTS
Re-enable interrupts and clear C to indicate success before
returning from a routine. Common pattern.
Not creative. Not copyrightable.
+5
View File
@@ -0,0 +1,5 @@
Setup VIC-II registers and load A with 0
$E5A0 is the location of the VIC-II register setup routine,
and so a call to that routine is to be expected.
Not creative. Not copyrightable.
+6
View File
@@ -0,0 +1,6 @@
SEC / JSR $FF99 - Read top of memory using public KERNAL API
Calling a public API function intended for use by user programs
cannot possibly be copyright. Even if it were, the publication of
the API would be strong evidence of an implied license to call the
API.
+3 -3
View File
@@ -1,4 +1,4 @@
fragment / BNE <skip following JMP instruction> / JMP somewhere
instruction fragment followed by conditional jump.
Conditionally jump somewhere. Would be a single instruction
on many architectures. Not copyrightable.
Would be single instruction on most architectures.
Very common idiom. No creativity. Not copyrightable.
+1
View File
@@ -0,0 +1 @@
The string "LOAD". Not copyrightable
+6
View File
@@ -0,0 +1,6 @@
JSR (output carriage return) + fragment
P217 of Compute's Mapping the 64 documents this
location as being the specified routine, so a call to it
should not be surprising. Not creative. Not copyrightable.
+3
View File
@@ -0,0 +1,3 @@
Store X and Y in ZP location pair
Nothing creative. Nothing copyrightable.
+3
View File
@@ -0,0 +1,3 @@
STA somewhere offset by X, increment X -- Loop fragment
Nothing creative nor copyrightable here.
+3
View File
@@ -0,0 +1,3 @@
subtract something from a ZP location
Common pattern. Not creative. Not copyrightable.
+3
View File
@@ -0,0 +1,3 @@
Subtract the contents of one ZP location from the contents of another.
Common pattern. Nothing creative. Not copyrightable.
+6
View File
@@ -0,0 +1,6 @@
Push memory location to stack
Would be single instruction on many architectures.
Stack is designed for storing things.
Not creative.
Not copyrightable.
+1
View File
@@ -0,0 +1 @@
Fragments of instructions. Not copyrightable.
+4
View File
@@ -0,0 +1,4 @@
increment a pointer in ZP
Common pattern, e.g., http://www.obelisk.me.uk/6502/algorithms.html
Not creative. Not copyrightable.
+3
View File
@@ -0,0 +1,3 @@
fragment + branch based on comparison of A with constant.
Common pattern. Not creative. Not copyrightable.
+4
View File
@@ -0,0 +1,4 @@
instruction fragments.
Not creative. Not copyrightable.
Not even a single whole instruction