whichbas: commentary cosmetics.

1 files changed, 11 insertions, 10 deletions

diff --git a/whichbas.c b/whichbas.c
index 168e052..c6673e9 100644
--- a/whichbas.c
+++ b/whichbas.c
@@ -214,8 +214,7 @@ CALLBACK(handle_cmd) {
 		set_type(BT_INVALID);
 	}
 
-	/* we have tokens 0x3a to 0x68 in both TB and BXE, or 47
-	   of them.
+	/* 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
@@ -226,20 +225,22 @@ CALLBACK(handle_cmd) {
       0x49: LOCK or UNPROTECT (take the same args)
       0x4B: RENAME in both Turbo and BXL/XE (same token, same args)
 
-		4 of them, this leaves 43 we can check.
+      4 of them, this leaves 43 we can check.
 
-		Covered so far: 41 (95%)
+      Covered so far: 41 (95%).
+      However, some of these are marked PARTIAL because they're not detected
+      under all circumstances.
 
       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
-		      exist, and we *do* catch the PROCEDURE token.
+            This isn't really important, as CALL requires a PROCEDURE to
+            exist, and we *do* catch the PROCEDURE token.
       0x5F: PAINT (req 2 args) or NUM (optional 2 args).
-		      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).
-	 */
+            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).
+    */
 	switch(tok) {
 		case 0x39: /* MOVE <args> or ENDWHILE */
 		case 0x3a: /* -MOVE <args> or TRACEOFF */