Difference between revisions of "BCALLs Template"

From WikiTI
Jump to: navigation, search
m (Destroys: capitalized AF)
 
(15 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 +
'''Note:''' Do not take the information on this template page as actual documentation!
 +
 +
Use this template for ROMCalls on calculators that don't use banked OS calls. Simply replace every occurance of bcall/BCALL/b_call with romcall/ROMCall/call.
 +
 +
The BCALLs are named by their b_call address, in hexadecimal. An example is [[83Plus:BCALLs:4009]].
 +
 +
Also, please put the following code (edited to reflect your call) in your page:
 +
<nowiki>[[Category:83Plus:BCALLs:By Name|ProveTheRiemannHypothesis]]
 +
[[Category:83Plus:BCALLs:By Name:Utility|ProveTheRiemannHypothesis]]
 +
[[Category:83Plus:BCALLs:By Address|0042 - ProveTheRiemannHypothesis]]</nowiki>
 +
This will cause your page to show in the appropriate categories. (Change the ProveTheRiemannHypothesis, 0042, and Utility to match your call. Also, change the 83Plus to whatever category, and change the BCALLs to ROMCalls if needed.) You may put a BCALL in any number of "By Name" categories. Put it in all the ones that make sense.
 +
 +
----
 +
 
== Synopsis ==
 
== Synopsis ==
'''Official Name:''' SomeCall
+
'''Official Name:''' ProveTheRiemannHypothesis
  
 
'''BCALL Address:''' 0042
 
'''BCALL Address:''' 0042
 +
''Use "Call Address" for regular 83.''
  
This ROM Call does absolutely nothing since it doesn't exist. :)
+
Proves the Riemann Hypothesis, storing the proof in an AppVar.
  
 
=== Inputs ===
 
=== Inputs ===
* a: Page to look copy from
+
* [[83Plus:RAM:8478|OP1]]: AppVar to save proof into
* de: Address to copy to
+
* HL: Maximum length of proof, in pages (must be at least 200)
* hl: Address to copy from
+
* bit proofCorrect, (iy + proofFlags): Set to generate a correct proof
* (de): A byte is copied from here
+
<!-- We need to figure out how we're doing flags and link that up -->
* [[83Plus:RAM:keyExtend|keyExtend]]: An example of a known RAM block.
+
* bit exampleBit, (iy+demoBye): Set to do something, reset to do s omething else
+
*Parity: Set for something
+
  
 
=== Outputs ===
 
=== Outputs ===
*(hl): A byte is copied to here
+
* Proof stored in AppVar
*Zero: Set if successful
+
* Zero Flag: Set if successful
  
=== Registers Destroyed ===
+
=== Destroys ===
*af
+
* AF
 +
 
 +
== Comments ==
 +
This B_CALL proves the Riemann Hypothesis, giving a proof under the required number of pages. It does this by randomly guessing proofs until it finds one that works. Needless to say, the calculator's batteries will run out before this B_CALL completes.
  
 
== Example ==
 
== Example ==
  <nowiki>ld a,$08
+
  <nowiki>ld hl, ProofAppVar
ld de,$567A
+
rst rMOV9TOOP1
ld hl,keyExtend
+
ld hl, 1000
b_call SomeCall</nowiki>
+
B_CALL ProveTheRiemannHypothesis</nowiki>
 +
 
 +
== Credits and Contributions ==
 +
* '''/dev/null:''' For not answering my questions about this B_CALL

Latest revision as of 08:45, 24 April 2005

Note: Do not take the information on this template page as actual documentation!

Use this template for ROMCalls on calculators that don't use banked OS calls. Simply replace every occurance of bcall/BCALL/b_call with romcall/ROMCall/call.

The BCALLs are named by their b_call address, in hexadecimal. An example is 83Plus:BCALLs:4009.

Also, please put the following code (edited to reflect your call) in your page:

[[Category:83Plus:BCALLs:By Name|ProveTheRiemannHypothesis]]
[[Category:83Plus:BCALLs:By Name:Utility|ProveTheRiemannHypothesis]]
[[Category:83Plus:BCALLs:By Address|0042 - ProveTheRiemannHypothesis]]

This will cause your page to show in the appropriate categories. (Change the ProveTheRiemannHypothesis, 0042, and Utility to match your call. Also, change the 83Plus to whatever category, and change the BCALLs to ROMCalls if needed.) You may put a BCALL in any number of "By Name" categories. Put it in all the ones that make sense.


Synopsis

Official Name: ProveTheRiemannHypothesis

BCALL Address: 0042 Use "Call Address" for regular 83.

Proves the Riemann Hypothesis, storing the proof in an AppVar.

Inputs

  • OP1: AppVar to save proof into
  • HL: Maximum length of proof, in pages (must be at least 200)
  • bit proofCorrect, (iy + proofFlags): Set to generate a correct proof

Outputs

  • Proof stored in AppVar
  • Zero Flag: Set if successful

Destroys

  • AF

Comments

This B_CALL proves the Riemann Hypothesis, giving a proof under the required number of pages. It does this by randomly guessing proofs until it finds one that works. Needless to say, the calculator's batteries will run out before this B_CALL completes.

Example

ld  hl, ProofAppVar
rst rMOV9TOOP1
ld  hl, 1000
B_CALL ProveTheRiemannHypothesis

Credits and Contributions

  • /dev/null: For not answering my questions about this B_CALL