User`s guide
The SEE Editor Environments
The SEE editor displays on the monitor of older terminal-based systems, or in a "monitor"
window within a PC graphics-based system (such as AdeptWindows). The majority of the
functions are identical, regardless of the environment in which the SEE editor runs. Note
that Adept DeskTop and Adept ACE provide enhanced program editors that include color-
coding, syntax help, and other features that are not available in the SEEeditor. For details,
see the Adept DeskTop User's Guide and the Adept ACE User's Guide.
Using Text Editors Other Than the SEE Editor
Programs can be written using any editor that creates a DOS ASCII text file. These programs
can then be stored on a V+ compatible disk (see the FORMAT command in the V+ Language
Reference Guide), LOADed into system memory, and opened by the SEE editor. When the
program is loaded, a syntax check is made. Programs that fail the syntax check will be
marked as nonexecutable. These programs can be opened in the SEE editor and any
nonconforming lines are marked with a question mark. Once these lines have been
corrected, the program can be executed.
In order for program files created outside of the SEE editor to LOAD correctly, the following
requirements must be met:
l Each program must begin with a .PROGRAM() line.
l Each program must end with an .END line (this line is automatically added by the SEE
editor but must be explicitly added by other editors).
l Each program line must be terminated with a carriage-return/line-feed (ASCII
13/ASCII 10).
l The end of the file (not the end of each program) must be marked with a Control-Z
character (ASCII 27).
l Lines that contain only a line-feed (ASCII 10) are ignored.
l Although fonts and spacing within files are not significant to the Adept system, in
order to have the text look the same as it would in one of the Adept environments, a
fixed-space font (e.g., Courier) and 8-space tab settings should be used.
The features of the SEE editor window are shown in the figure below.
The SEE Editor Environments
(Undefined variable: Primary.Product_Name_V)Language User's Guide, version
17.x
Page 27