jump table now uses vectors in RAM

strings/036C1C036C

@@ -1,3 +0,0 @@
-$03 (most likely adddress higher byte) + JMP ($031C) (via public, documented vector) + JMP (address does not match)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.

strings/036C1E036C

@@ -1,3 +0,0 @@
-$03 (most likely adddress higher byte) + JMP ($031E) (via public, documented vector) + JMP (address does not match)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.

strings/036C20036C

@@ -1,3 +0,0 @@
-$03 (most likely adddress higher byte) + JMP ($0320) (via public, documented vector) + JMP (address does not match)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.

strings/036C22036C

@@ -1,3 +0,0 @@
-$03 (most likely adddress higher byte) + JMP ($0322) (via public, documented vector) + JMP (address does not match)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.

strings/036C24036C

@@ -1,3 +0,0 @@
-03 (most likely adddress higher byte) + JMP ($0324) (via public, documented vector) + JMP (address does not match)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.

strings/036C2603

@@ -1,3 +0,0 @@
-$03 (most likely adddress higher byte) + JMP ($0326) (via public, documented vector)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.

strings/036C2A036C

@@ -1,4 +0,0 @@
-$03 (most likely adddress higher byte) + JMP ($032A) (via public, documented vector) + JMP (address does not match)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.
-

strings/036C2C03

@@ -1,3 +0,0 @@
-$03 (most likely adddress higher byte) + JMP ($032C) (via public, documented vector)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.

strings/6C1A036C

@@ -1,3 +0,0 @@
-JMP ($031A) (via public, documented vector) + JMP (address does not match)
-
-Code similarity due to Kernal API usage convention. Since 6510 CPU does not have indirect JSR, the only sane possibility to use Kernal API vectors in RAM ($0314-$0333) is to have JMP ($address) hardcoded somewhere. The jump table has intentionally strange order (to avoid code similarity as much as possible), but some small similarities can't be avoided in any reasonable way.