aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--whichbas.c21
1 files changed, 14 insertions, 7 deletions
diff --git a/whichbas.c b/whichbas.c
index 9031442..3d15f01 100644
--- a/whichbas.c
+++ b/whichbas.c
@@ -189,19 +189,22 @@ CALLBACK(handle_cmd) {
/* we have tokens 0x3a to 0x68 in both TB and BXE, or 47
of them.
+
Some tokens can't be determined, because they take the
same argument (or lack of) in both Turbo and BXL/XE. These
are:
+
0x3c: REPEAT or ELSE (no args either way)
0x46: LOOP or CP (no args either way)
0x49: LOCK or UNPROTECT (take the same args)
- 0x4B: RENAME in both Turbo and BXL/XE (take the same args)
- This leaves 42 we can check.
- Covered so far: 39 (93%)
- TODO: Unknown tokens:
- 0x5A: BLOAD or... what? (Jindroush lists it as BXL_EXTEND for BXL and
- ?5A? for BXE)
- TODO:
+ 0x4B: RENAME in both Turbo and BXL/XE (same token, same args)
+
+ 4 of them, this leaves 43 we can check.
+
+ Covered so far: 40 (93%)
+
+ Unchecked tokens:
+
0x5B: BRUN or CALL (both take a string, CALL allows "USING" though)
This isn't really important, as CALL requires a PROCEDURE to
exit, and we *do* catch the PROCEDURE token.
@@ -209,6 +212,10 @@ CALLBACK(handle_cmd) {
Again, not important, because it's highly unlikely any BXL/BXE
program will contain NUM... because when it executes, it stops the
program and goes back to the READY prompt (in auto-numbering mode).
+
+ TODO: Unknown token, find out what it does:
+ 0x5A: BLOAD or... what? (Jindroush lists it as BXL_EXTEND for BXL and
+ ?5A? for BXE)
*/
switch(tok) {
case 0x39: /* MOVE <args> or ENDWHILE */