83Plus:Hooks:9BAC - Revision history

Thepenguin77: Added mode 0 tidbit

2010-04-10T21:41:19Z

Added mode 0 tidbit

FloppusMaximus: New information on condition 0

2007-02-18T06:43:20Z

New information on condition 0

84plusfreak: /* Class 3 Functions */

2006-05-18T13:36:51Z

‎Class 3 Functions

Aquanight: Fixed flag link.

2005-07-19T00:30:39Z

Fixed flag link.

84plusfreak: /* Class 3 Functions */ -Arguments

2005-04-27T18:08:27Z

‎Class 3 Functions: -Arguments

FloppusMaximus at 05:13, 30 March 2005

2005-03-30T05:13:53Z

FloppusMaximus: categorized

2005-03-28T16:59:41Z

categorized

FloppusMaximus at 07:42, 28 March 2005

2005-03-28T07:42:00Z

FloppusMaximus at 07:04, 28 March 2005

2005-03-28T07:04:49Z

FloppusMaximus at 06:50, 28 March 2005

2005-03-28T06:50:18Z

New page

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

The Hooks are named by their hook pointer block address (the four bytes consisting of page, address, and an extra byte), in hexadecimal. An example is [[83Plus:Hooks:9B84]].

----

== Synopsis ==
'''Name:''' ImAHook

'''Hook Pointer Block Address:''' [[83Plus:RAM:8562|8562]]

'''Hook Enable BCALL:''' [[83Plus:BCALLs:1234|1234]]

'''Hook Disable BCALL:''' [[83Plus:BCALLs:5678|5678]]

'''Hook Call BCALL:''' [[83Plus:BCALLs:9012|9012]]

'''Hook Active Flag:''' 6, (iy + 23h)

This hook allows you to change the values that [[83Plus:BCALLs:4972|GetKey]] returns.

== Using the Hook ==
These different values, passed in a, determines what the hook should do.
* 1: The calculator just turned on. There seem to be no other values passed to the hook.
* 2: The calculator is computing 1+1.
** b: 1
** c: 1
** Change b and/or c to affect the output of the problem (which will still look like 1+1 to the user).
* 3: Preparing to turn off due to 2nd+OFF.
** Zero flag: Clear to abort the power off.

== Comments ==
This hook doesn't exist. This is a demonstration only.

== Credits and Contributions ==
* '''/dev/hda1:''' My favorite hard drive partition.

@@ Line 20: / Line 20: @@
 ** [[83Plus:RAM:9652|parseVar]] = name of variable being parsed
 ** ([[83Plus:RAM:965B|begPC]]), ([[83Plus:RAM:965D|curPC]]), and ([[83Plus:RAM:965F|endPC]]) are set to the start, current location and end of the variable respectively
 ** Return Z if the parser should continue parsing this variable.
 * 1-3: A BASIC function has been encountered.  The various types are described below.

@@ Line 17: / Line 17: @@
 == Using the Hook ==
 These different values, passed in A, determine what the hook should do.
-* 0: The calculator is about to parse a variable.
+* 0: The parser has just been restarted.  This happens when the calculator begins parsing a variable, as well as after some control statements. ''Do not assume that OP1 is the name of the variable being parsed!''
-** OP1 = name of variable to be parsed.
+** [[83Plus:RAM:9652|parseVar]] = name of variable being parsed
-** Return Z if the variable should be parsed normally.
+** ([[83Plus:RAM:965B|begPC]]), ([[83Plus:RAM:965D|curPC]]), and ([[83Plus:RAM:965F|endPC]]) are set to the start, current location and end of the variable respectively
 * 1-3: A BASIC function has been encountered.  The various types are described below.
 ** BC identifies the particular function within the class.  For many 1-byte tokens, B is the token itself; for many others, B is the OP-number given in ti83plus.inc (although some of these are incorrect.)
@@ Line 61: / Line 62: @@
          jr nz,ReturnZ
          ld hl,EXECStr       ; Check whether our string
-         ld de,OP1+1         ; matches the name to be run.
+         ld de,parseVar+1    ; matches the name to be run.
          call CompStrs       ; Will return NZ if they don't match
          jr nz,ReturnZ

@@ Line 50: / Line 50: @@
 If very little is known about class 2, less is known about class 3.  Tenatively, it looks like the class 2 functions that you would expect to be class 1 have class 3 secondary callbacks.
-It looks like the parameters are stored in OP1 and the FPS as in class 1 and the number of arguments is stored at [[83Plus:RAM:9661|9661]]. HL is the same as (OPS) and should saved.
+It looks like the parameters are stored in OP1 and the FPS as in class 1 and the number of arguments is stored at [[83Plus:RAM:9661|9661]]. HL is the same as (OPS) and should be saved.
 == Examples ==

@@ Line 36: / Line 36: @@
 * Modify arguments, or add or remove them while updating HL appropriately, and return Z.
 * Remove all arguments from the FPS, place the result of your computation in OP1, and return NZ.
-* Remove all arguments from the FPS, reset [[83Plus:Flags:7#Bit0|numOP1,(iy+ParsFlag2)]], and return NZ.  (This is generally preferable if you are not returning a useful value, as it will preserve Ans.)
+* Remove all arguments from the FPS, reset [[83Plus:Flags:07#Bit0|numOP1,(iy+ParsFlag2)]], and return NZ.  (This is generally preferable if you are not returning a useful value, as it will preserve Ans.)
 === Class 2 Functions ===

@@ Line 50: / Line 50: @@
 If very little is known about class 2, less is known about class 3.  Tenatively, it looks like the class 2 functions that you would expect to be class 1 have class 3 secondary callbacks.
-It looks like the parameters are stored in OP1 and the FPS as in class 1, but there is the rather significant problem that the number of arguments is not in HL.  If it's stored somewhere else, I don't know about it, though I haven't looked very hard.
+It looks like the parameters are stored in OP1 and the FPS as in class 1 and the number of arguments is stored at [[83Plus:RAM:9661|9661]]. HL is the same as (OPS) and should saved.
 == Examples ==

@@ Line 1: / Line 1: @@
-[[Category:83Plus:Hooks:By_Name|Parser Hook]]
+[[Category:83Plus:Hooks:By_Name|Parser Hook]] [[Category:83Plus:Hooks:By_Address|9BAC - Parser Hook]]
 [[Category:83Plus:Hooks:By_Address|9BAC - Parser Hook]]
 == Synopsis ==
 '''Name:''' Parser Hook

← Older revision		Revision as of 16:59, 28 March 2005
Line 1:		Line 1:
		+	[[Category:83Plus:Hooks:By_Name\|Parser Hook]]
		+	[[Category:83Plus:Hooks:By_Address\|9BAC - Parser Hook]]
	== Synopsis ==		== Synopsis ==
	'''Name:''' Parser Hook		'''Name:''' Parser Hook

@@ Line 50: / Line 50: @@
 It looks like the parameters are stored in OP1 and the FPS as in class 1, but there is the rather significant problem that the number of arguments is not in HL.  If it's stored somewhere else, I don't know about it, though I haven't looked very hard.
 == Credits and Contributions ==
 * '''Brandon Sterner:''' Analysis, and the Symbolic source code.
 * '''Michael Vincent:''' The Omnicalc source code.

@@ Line 1: / Line 1: @@
-'''Note:''' Do not take the information on this template page as actual documentation!
+== Synopsis ==
-The Hooks are named by their hook pointer block address (the four bytes consisting of page, address, and an extra byte), in hexadecimal. An example is [[83Plus:Hooks:9B84]].
+'''Hook Pointer Block Address:''' [[83Plus:RAM:9BAC|9BAC]]
-----
+'''Hook Enable BCALL:''' [[83Plus:BCALLs:5026|5026]]
-== Synopsis ==
+'''Hook Disable BCALL:''' [[83Plus:BCALLs:5029|5029]]
-'''Name:''' ImAHook
-'''Hook Pointer Block Address:''' [[83Plus:RAM:8562|8562]]
+'''Hook Call BCALL:''' ''(none known)''
-'''Hook Enable BCALL:''' [[83Plus:BCALLs:1234|1234]]
+'''Hook Active Flag:''' [[83Plus:Flags:36#Bit_1|1, (iy + 36h)]]
-'''Hook Disable BCALL:''' [[83Plus:BCALLs:5678|5678]]
+This hook allows you to change the behavior of the TI-BASIC parser and functions.
-'''Hook Call BCALL:''' [[83Plus:BCALLs:9012|9012]]
+== Using the Hook ==
-'''Hook Active Flag:''' 6, (iy + 23h)
+=== Class 1 Functions ===
-This hook allows you to change the values that [[83Plus:BCALLs:4972|GetKey]] returns.
+Class 1 tokens all take some positive number of arguments (zero arguments is a syntax error.)  These are separated by commas, or in the case of binary operators, by the operator itself. All of the arguments are evaluated before the function is.
-== Using the Hook ==
+The arguments are placed on the FPS in "reverse" order.  That is to say, the earliest argument read is deepest in the stack. The final argument is in OP1.  The total number of arguments is passed in HL.
-These different values, passed in a, determines what the hook should do.
-* 1: The calculator just turned on. There seem to be no other values passed to the hook.
+Any of the following data types may be used (except where prohibited by syntax rules): Real, List, Matrix, Equation, String, Complex, Complex List.  Real numbers are stored on the stack as floating-point. Complex numbers are stored as two consecutive stack entries or in OP1 and OP2 (see the SDK documentation for Push/Pop OP1/3/5.)  Other data types are stored as variable names.
-* 2: The calculator is computing 1+1.
-** b: 1
+A hook may do any of the following:
-** c: 1
+* Leave all arguments as is, and return Z.
-** Change b and/or c to affect the output of the problem (which will still look like 1+1 to the user).
+* Modify arguments, or add or remove them while updating HL appropriately, and return Z.
-* 3: Preparing to turn off due to 2nd+OFF.
+* Remove all arguments from the FPS, place the result of your computation in OP1, and return NZ.
-** Zero flag: Clear to abort the power off.
+* Remove all arguments from the FPS, reset [[83Plus:Flags:7#Bit0|numOP1,(iy+ParsFlag2)]], and return NZ.  (This is generally preferable if you are not returning a useful value, as it will preserve Ans.)
-== Comments ==
+It looks like the parameters are stored in OP1 and the FPS as in class 1, but there is the rather significant problem that the number of arguments is not in HL.  If it's stored somewhere else, I don't know about it, though I haven't looked very hard.
-This hook doesn't exist. This is a demonstration only.
 == Credits and Contributions ==
-* '''/dev/hda1:''' My favorite hard drive partition.
+* '''Brandon Sterner:''' Analysis, and the Symbolic source code.