Category:83Plus:OS:Operator Stack - Revision history

NonstickAtom at 19:39, 3 December 2020

2020-12-03T19:39:20Z

NonstickAtom at 19:19, 3 December 2020

2020-12-03T19:19:17Z

NonstickAtom: Wikified but I don't want to move it because I'm still new :P Also I don't know if putting two memory locations is allowed.

2020-12-03T19:17:46Z

Wikified but I don't want to move it because I'm still new :P Also I don't know if putting two memory locations is allowed.

Glenafer at 23:48, 3 September 2008

2008-09-03T23:48:50Z

Taricorp: stub

2007-06-28T22:16:32Z

stub

Taricorp at 22:12, 28 June 2007

2007-06-28T22:12:27Z

New page

{{Wikify}}
The operator stack is defined between (OPS) and (OPBase). The OS uses this area for storing information, along with the FPS, for conditional statements and loops in TI-BASIC. Due to extremely poor programming in the OS, this is the cause of the well-known memory leaks which can occur if a programmer uses a Goto statement within a loop or If:Then statement (In a nutshell, it moves the OPS and FPS by nine bytes every time a push to each occurs (enter a conditional), which can cause a slowdown (slowly becomes more to move) and memory leaks (the nine bytes added above (?) the FPS are not accounted for, or are 'leaked'.).

Very little is currently known about the OPS since TI has not documented it, but research is underway.

← Older revision		Revision as of 19:39, 3 December 2020
Line 1:		Line 1:
−	~~{{Wikify}}~~
	{{stub}}		{{stub}}

@@ Line 4: / Line 4: @@
 == Synopsis ==
-'''Official Name:''' OPBase and OPS
+'''Official Name:''' OPS
-'''Memory Address:''' 9826h - 9828h
+'''Memory Address:''' 9828h
 '''Length:''' 2 bytes

@@ Line 1: / Line 1: @@
 {{Wikify}}
 {{stub}}
-Due to extremely poor programming in the OS, it is the cause of the well-known memory leaks which can occur if a programmer uses a Goto statement within a loop or an If:Then statement.  In a nutshell, it moves the OPS and FPS by nine bytes every time a push to each occurs, which happens when a conditional is entered.  This can cause a slowdown (slowly becomes more to move) and memory leaks (the nine bytes added above).  The FPS are not accounted for, or are 'leaked'.
+== Synopsis ==
 Very little is currently known about the OPS since TI has not documented it, but research is underway.