RANDOMIZE
10 RANDOMIZE 20 x = RND PRINT x 30 END RNH .244013674718 INTOUCH RNH .524856061388
? RANDOMIZE gives the RND function a new starting point. G This ensures that you will get a different random number sequence each time your program executes.
I INTOUCH uses a list of random numbers when the RND function is used. If I no RANDOMIZE statement is used, INTOUCH starts at the same place in this K list each time the program executes. This means the same series of random 4 numbers is returned each time the program executes.
K RANDOMIZE tells INTOUCH to pick a random starting point in the list. This H ensures that a different series of random numbers is returned each time 0 the program executes. (See RND for information on the RND function.)
K INTOUCH detects and announces run-time and compile-time errors. Sometimes K errors occur which don't prevent execution, but cause a program to execute G incorrectly. INTOUCH provides a high-level DEBUG system for detecting these more subtle errors.
J DEBUG ON enables INTOUCH's Debug System. DEBUG OFF disables the system. I When DEBUG is enabled, a DEBUG flag will appear at the status message in K the upper right corner of the INTOUCH screen. When DEBUG is disabled, the M flag disappears from the screen. DEBUG ON turns on the frame if it was off.
> The related function for the INTOUCH Debug System is _DEBUG. ) See _DEBUG for information on the _DEBUG system function.
G Some DEBUG features automatically switch DEBUG ON or OFF when they are B executed. Others require that DEBUG be enabled. (See DEBUG ON.)
Note
I Using the debugging facilities impacts the INTOUCH system's performance. L The system has been designed for optimal performance in a normal production @ environment. Therefore, DEBUG will slow INTOUCH response time.
DEBUG ON
DEBUG ON 1050 DEBUG ON
A Use DEBUG ON to enable INTOUCH's debug system. The DEBUG G system helps you find problems in the way your program runs. You must 0 enable the system in order to use its features.
F When DEBUG is enabled, all of INTOUCH's DEBUG features are available. I DEBUG remains enabled until a DEBUG OFF command or statement is executed 8 or until a DEBUG feature is executed which disables it.
I DEBUG ON can be issued in immediate mode or as a statement in a program. K If DEBUG ON is used in a program, INTOUCH enables DEBUG when it encounters J the DEBUG ON statement. After you turn DEBUG ON, you must use RUN or RNH < to start the program before you can use the STEP statement.
DEBUG OFF
DEBUG OFF 1050 DEBUG OFF
= Use DEBUG OFF to disable INTOUCH's DEBUG system. You F should turn DEBUG OFF when you have finished correcting your program.
J DEBUG OFF can be issued in immediate mode or as a statement in a program. B If DEBUG OFF is used in a program, INTOUCH disables DEBUG when it $ encounters the DEBUG OFF statement.
F DEBUG will remain disabled until a DEBUG ON statement is executed, or 4 until a DEBUG feature is executed which enables it.
C 4.5 Monitoring Program Execution
I DEBUG's TRACE and STATISTICS features monitor your program's execution. : These features take effect only during program execution.
H TRACE traces your program line by line as it executes. TRACE lists the C number of each program line as it is executed. STATISTICS records K information on your program's execution. It records the time each program J line takes to execute and the number of times the line is executed. The F word "STATISTICS" can be abbreviated to "STATS" (STATS ON, STATS OFF, G LIST STATS). This abbreviation will be used frequently in this Guide.
H 4.6 The TRACE and STATISTICS Features
A Both the TRACE and STATISTICS features operate on program lines. > A number of program lines can be attached to one line number.
10 PRINT a$ PRINT b$ PRINT c$
K The TRACE feature notes these program lines by line number. For instance:
10 PRINT a$ --- 10
H If more than one program line is attached to a line number, the program > lines are denoted by a period and the number of the sub-line.
10 PRINT a$ --- 10 PRINT b$ --- 10.1 PRINT c$ --- 10.2
G In the example above, the first line is noted as 10. The program line E following the first line is 10.1. The next line is 10.2 and so on. 0 Labels are noted in the same way. For example:
$ 10 show: PRINT a$ --- SHOW & PRINT b$ --- SHOW.1 & PRINT c$ --- SHOW.23
TRACE ON
TRACE ON 1050 TRACE ON
= Use TRACE ON to turn INTOUCH's trace feature on. The G trace feature lists the number of each program line as it is executed. F Use TRACE to see if your statements are being executed in the correct ' order and the correct number of times.
* To use TRACE, you must have the frame on.
H TRACE ON enables INTOUCH's trace feature. The trace feature lists each J program line as it is executed. TRACE ON can be executed as a command or N as a statement. If TRACE ON is executed as a command, DEBUG is automatically H switched on. If TRACE ON is executed as a statement, and DEBUG is off, J INTOUCH ignores the TRACE ON. The following program is executed with the trace feature on:
10 DIM name$(5) ! MAIN: FOR i = 1 TO 5 = INPUT 'Please enter your name': name$(i) . IF _EXIT THEN EXIT FOR 3 PRINT 'Hello, '; name$(i); '!' NEXT i 20 END
W INTOUCH 4.2 Program: NONAME DEBUG W The Next Generation Language Status : RUN INTOUCH TRACE ON INTOUCH RNH Please enter your name? John Hello, John! Please enter your name? W [10] [MAIN] [MAIN.1] [MAIN.2] [MAIN.3] [MAIN.4] [MAIN.1] W W EXIT = Exit \ = Back HELP = Help
F The trace remains in effect until a TRACE OFF command or statement is F executed. When program execution stops, the trace stops. If program E execution continues and the TRACE ON command is still in effect, the trace continues.
TRACE OFF
TRACE OFF 1050 TRACE OFF
4 Use TRACE OFF to turn the trace feature off.
E TRACE OFF disables the trace feature. INTOUCH stops listing program H line numbers when TRACE OFF is executed. If TRACE OFF is executed as a H statement in a program and DEBUG is off, INTOUCH ignores the statement.
STATS ON
STATS ON 1020 STATS ON
= Use STATS ON to turn on the statistics feature, which I stores the execution time and count for each program line. Use STATS to G tell if your statements are being executed the correct number of times D and which parts of your program are taking the most time. STATS is A especially useful for speeding up your program's execution time.
I STATS ON enables INTOUCH's statistics feature. INTOUCH begins recording J statistics when program execution begins. The statistics feature remains 3 enabled until the STATS OFF statement is executed.
I STATS ON can be executed in immediate mode or in a program. If STATS ON G is executed in immediate mode, DEBUG is automatically switched on. If I STATS ON is executed in a program, and DEBUG is off, INTOUCH ignores the J statement. When STATS ON is executed, any statistics previously recorded are lost.
STATS OFF
STATS OFF 1020 STATS OFF
9 Use STATS OFF to turn off the statistics feature.
D STATS OFF turns off INTOUCH's statistics feature. STATS OFF can be F executed in immediate mode or in a program. If STATS OFF is executed ? in a program and DEBUG is off, INTOUCH ignores the statement. STATS OFF leaves DEBUG on.
C LIST STATS [:label | line_num [- | ,] label | line_num...]
LIST STATS
< Use LIST STATS to display the statistics recorded by the STATISTICS feature.
K LIST STATS lists each program line along with the number of times the line 2 was executed and the execution time of each line.
W INTOUCH 4.2 Program: NONAME STATS DEBUG W The Next Generation Language Status : RUN INTOUCH LIST STATS NONAME 4-MAY-1995 00:54 - 1 0.00 10 DIM name$(5) 5 1 0.00 MAIN: FOR i = 1 TO 5 Q 5 16.64 INPUT 'Please enter your name': name$(i) B 5 0.00 IF _EXIT THEN EXIT FOR G 5 0.00 PRINT 'Hello, '; name$(i); '!' - 5 0.00 NEXT i $ 1 0.00 20 END INTOUCH W W EXIT = Exit \ = Back HELP = Help
K The far-left column lists the number of times each statement was executed. I The next column gives the time each statement took to execute. The time H is given in seconds and fractions of a second. (0.01 means the program L line was executed in one-one hundredth of a second.) The last column lists E the program itself. STATS must be ON for LIST STATS to be executed.
G All the options available with the "LIST" statement are also available 7 with LIST STATS. (See Section 2.3.7, LIST for listing information.)
BREAK
1050 BREAK
= Use BREAK to stop program execution when DEBUG is ON. G For instance, you might use BREAK to stop the program if a variable is assigned a wrong value.
L The BREAK statement can be used anywhere in a program. The BREAK statement J will not take effect unless DEBUG is turned on. If DEBUG is off, INTOUCH ignores any BREAK statements.
I When INTOUCH executes a BREAK statement, it interrupts program execution I and prints a BREAK message. The BREAK message tells what line the break E occurred in. Program execution can be continued with the GO or STEP commands.
W INTOUCH 4.2 Program: NONAME DEBUG W The Next Generation Language Status : BREAK at 10.2 10 PRINT '1', PRINT '2', BREAK PRINT '3', PRINT '4', PRINT '5' 20 END DEBUG ON INTOUCH RNH 6 1 2 BREAK at 10.2 INTOUCH W W EXIT = Exit \ = Back HELP = Help
STEP [number]
STEP STEP 10 C Use STEP to execute a specific number of program statements L and then stop execution. That way, you can "step through" your program to find bugs.
J STEP is used to step through your program---to execute a specified number N of program statements. DEBUG must be ON for the STEP command to take effect. L If DEBUG is not on and the STEP command is given, INTOUCH ignores it. STEP N must be given as a command. When the STEP command has been executed, INTOUCH O issues a BREAK and prints the break message. Issuing the STEP command without 5 a number causes INTOUCH to execute one program line.
W INTOUCH 4.2 Program: NONAME DEBUG W The Next Generation Language Status : BREAK at 10.5 RNH 6 1 2 BREAK at 10.2 INTOUCH STEP 2 3 4 INTOUCH W ^ PRINT '5' W EXIT = Exit \ = Back HELP = Help
E Issuing the STEP command with a number causes INTOUCH to execute the E number of program lines specified. INTOUCH begins executing program F lines from the last line executed. It stops when the number of lines = specified have been executed or when program execution ends.
E You must start a program with RUN or RNH before you can use the STEP statement.
G 4.8 GO--Continuing Program Execution
- 4.8.1 GO
GO
GO
> Use GO to continue program execution after it has been interrupted.
F Once execution has stopped, you can enter immediate mode and debugger E commands, change code, etc. GO lets you resume execution even after I code has been changed. If a HALT or BREAK statement was used, execution < will resume at the first statement after the HALT or BREAK.
W INTOUCH 4.2 Program: NONAME DEBUG W The Next Generation Language Status : BREAK at 20 10 DEBUG ON FOR i = 1 TO 6 20 IF i = 4 THEN BREAK 30 NEXT i 40 END RNH BREAK at 20 INTOUCH PRINT SQR(i) 2 INTOUCH 25 PRINT i; GO 4 5 6 INTOUCH W W EXIT = Exit \ = Back HELP = Help
D This chapter describes the various ways that data can be entered at ( the terminal and stored into variables.
! [LINE] INPUT var, var... . [KEY] [LINE] INPUT [ ['Prompt_text'] ( [, PROMPT str_expr] [, ERASE] F [, AT row, column] [, LENGTH num_expr] [, DEFAULT str_expr] H [, VALID str_expr] [, TIMEOUT time_limit] [, ELAPSED num_var] S [, AREA num_expr, num_expr, num_expr, num_expr] [, ATTRIBUTES attr_list] 0 [, SCREEN '[text] <format>...'] A [, MENU str_expr: str_var] :] var [,var. . .]
9 10 INPUT 'Please enter your first name': first$ 5 INPUT 'Now, enter your last name': last$ 2 LINE INPUT 'Where do you live': city$ 20 PRINT / PRINT 'Hello '; first$; ' '; last$ ! PRINT 'From '; city$ 30 END RNH , Please enter your first name? Sunny ' Now, enter your last name? Day 1 Where do you live? San Diego, California Hello Sunny Day # From San Diego, California
G Use the INPUT statement to ask questions at the terminal and store the ! answers for use in your program.
? The INPUT statement reads data typed by the user at the E terminal and assigns it to variables. var is a variable that J the data is being assigned to. When INTOUCH executes an INPUT statement, J it prints any prompt given and waits for the user's response. The user's 8 response is then assigned to the variable(s) specified.
J For information on INPUT from a text file, see Chapter 15, File Handling.
I The user enters data at the terminal in response to the INPUT statement. F The input data must be the same data type as the variable, or INTOUCH E generates an exception. If, in response to the INPUT statement, the , user presses the Return key and:
D 5.1.1 Types of INPUT Statements
+ There are three types of INPUT statements:
7There are four input styles:
2 10 INPUT 'Please enter your name': name$ " 20 PRINT 'Hello '; name$ 30 END RNH % Please enter your name? Toby Hello Toby
2 10 INPUT 'Please enter your name': name$ G 20 INPUT SCREEN 'Soc. sec.: <DIGITS: ###-##-####>': ssn 8 30 PRINT name$, 'Social security number:'; ssn 40 END RNH % Please enter your name? Fred 6 Soc. sec.: ___-__-____ (before input) 5 Soc. sec.: 324-11-4533 (after input) > Fred Social security number: 324114533
10 CLEAR - MESSAGE 'Press GOLD/F when done' 0 20 LINE INPUT AREA 5, 10, 8, 60: text$ - 30 PRINT AT 10, 1: 'Rewrapped text' & 40 wt$ = WRAP$(text$, 1, 30) 50 PRINT wt$ 60 END RNH 9 This is an example of wrapped text. The text is < wrapping.__________________________________________ < ___________________________________________________ < ___________________________________________________ Rewrapped text & This is an example of wrapped % text. The text is wrapping.
5 10 sample_menu$ = '%TITLE "Options",' & 1 + 'Add, Change, Delete, Inquire' 5 20 LINE INPUT MENU sample_menu$: selection$ 1 30 PRINT 'Menu option was '; selection$ 40 END RNH +--Options---+ | ADD | | CHANGE | | DELETE | | INQUIRE | +------------+ Menu option was CHANGE
L The INPUT statement has the following options. These options are described 1 in detail in following sections of this chapter.
| PROMPT | %displays the prompt text | |
| AT row, col | ?positions the cursor on the desired row and column | |
| LENGTH nn | Alimits the number of characters that a user can type | |
| DEFAULT | ;lets you provide defaults for INPUT statements | |
| VALID | %validates user responses | |
| TIMEOUT | Hlimits the time the user has to respond to the INPUT prompt | |
| AREA | Ndoes free format multi-line text input from an area on the screen | |
| SCREEN | 1creates formatted data entry screens | |
| MENU | <displays and receives input from "pop-up" menus | |
| ELAPSED | Tkeeps track of the time it takes the user to respond to an INPUT prompt | |
| ATTRIBUTES | 8displays in BOLD, BLINK, REVERSE, UNDERLINE | |
| ERASE | bclears the input line prior to accepting input and after the input has been completed |
G At an input prompt, there are several commands and keystrokes that the ? user can enter instead of an answer to the prompt. These are: "
@ You can type the word EXIT or press Ctrl/Z to F exit from a prompt or procedure. If one of these options is entered, > INTOUCH sets the internal variable _EXIT to TRUE (1).
"
/ If you enter \ (backslash) or press the 7 Up-arrow key, the internal variable _BACK will be set to TRUE (1).
A You can get help for an input item by typing the word HELP K or by pressing the Help key. If one of these options is input, = INTOUCH sets the internal variable _HELP to TRUE (1).
J The internal variables _BACK, _EXIT and _HELP can be examined within your - program and appropriate action can be taken.
H If the user wants to edit their input, they can use the following keys:
| Left-arrow | move left | |
| Right-arrow | move right | |
| Delete key | :delete character(s) to the left of the cursor | |
| TAB | 8move to next input field or terminate input | |
| CTRL/A | 6toggle between insert and overstrike mode | |
| CTRL/E | move to end of line | |
| CTRL/H | &move to beginning of line | |
| CTRL/J | 7delete the word to the left of the cursor. | |
| CTRL/U | 1delete all the characters on a line. | |
| Return | …terminate the input; you can press Return anywhere in the line, you do not have to be at the end of the line. |
4