Guardian Programmer's Guide

Using the IOEdit Procedures
Guardian Programmer’s Guide — 421922-014
14 - 4
Line Numbers and Records
Table 14-2 indicates when SIO works better than IOEdit.
See Section 15, Using the Sequential Input/Output Procedures, for details of using
SIO.
Line Numbers and Records
A line number identifies each line in an EDIT file. You can see the line numbers in an
EDIT file using the SHOWNUMBER EDIT command, for example:
1 ?INSPECT,SYMBOLS
1.001
1.1 ?NOLIST
2 ?SOURCE $SYSTEM.SYSTEM.EXTDECS0(WRITE,READ,FILE_OPEN_,
2.1 PROCESS_GETINFO_,WRITEREAD,NUMOUT)
3 ?LIST
4
5 PROC MYPROC MAIN;
6 BEGIN
6.003 STRING .TERM^NAME[0:ZSYS^VAL^LEN^FILENAME-1];
6.004 INT NAME^LEN;
6.01 INT TERM^NUM;
6.02 INT .BUFFER[0:127];
6.03 INT WCOUNT;
6.04 STRING .SBUFFER := @BUFFER '<<' 1;
6.05 INT .S^PTR;
6.06 INT ASCII[0:5];
6.07 INT NUM;
6.1
7 CALL PROCESS_GETINFO_(,,,,,TERM^NAME:ZSYS^VAL^LEN^FILENAME-1
,NAME^LEN);
8 CALL FILE_OPEN_(TERM^NAME:NAME^LEN,TERM^NUM);
.
.
Table 14-2. Advantages of SIO Over IOEdit
If you want to... Then SIO is better than IOEdit because...
Use an error file for reporting errors. SIO uses an error file; IOEdit does not.
Write long lines. SIO has a write-fold feature that allows a long line
t
o be divided into several shorter lines; IOEdit has
no such feature.
Perform I/O with file types other than
ED
IT files and T-Text files.
SIO is able to access many device and file types;
IOEdit can access only EDIT and T-Text files.