Figure 2-15. Starting Tedit From Tacl - HP TACL Programming Manual

Developing TACL Programs
Debugging TACL Programs
2–34
without accessibility to the #ARGUMENT built-in function, you would need to check
that the argument is a valid file name.

Figure 2-15. Starting TEDIT From TACL

?SECTION tedsave ROUTINE
#FRAME
#PUSH editfile
== Retrieve the first argument and place it into editfile:
[#CASE [#ARGUMENT /VALUE editfile/ FILENAME /SYNTAX/
OTHERWISE]
|1|
TEDIT [editfile]
#OUTPUT DONE WITH [#FILEINFO /FULLNAME/ [editfile]]
|2|
#OUTPUT *** Error:
] == end #CASE
#UNFRAME
When you run tedsave , it displays output similar to the following:
>2 tedsave sect08
Control passes to TEDIT. After the user exits from TEDIT, the routine displays:
DONE WITH $VOL.SUBVOL.SECT08
The following paragraphs describe a sample debugging session. The tedsave routine
is already loaded into memory:
3> BREAK tedsave
4> tedsave sect08
tedsave sect08
^
-BREAK-
On line 5, the user issues a STEP command and _DEBUGGER displays the next line of
the routine. The user then presses RETURN to continue stepping through the routine;
when the user steps through the routine in this way, the line number does not advance
(lines that show nothing but a line number are terminated by RETURN):
-5-STEP
#FRAME
-TRACE-
-6-
#PUSH editfile
-TRACE-
-6-
[#CASE [#ARGUMENT /VALUE editfile/ FILENAME /SYNTAX/
^
107365 Tandem Computers Incorporated
invalid filename ***