This is a sample of current work and contains a VIC command.
This work is - copyrighted 1994, 1995 by: Timothy V. Rue
timrue@mindspring.com
(see copyright information at end of document)
---------------------------------------------------------------------
| (SF) Sequence-Files (or Script-File) |
SF - edit script-file lines and/or process, and output
(SF) Sequence-Files - The concept of Sequence-Files is to access and
control the typical "grab the next line of the active
script-file", process it for VIC variables and commands, then
pass it on to the device or program-port as set by OP when
there is something to pass on (not completely consumed by
SF.) Contained in the PK-file is the current stack of SF
script-file name(s) with current line number(s) of execution
of the script-file(s). Through PK this stack of SF-file
name(s) and the line number(s) can be altered to change the
up and comming sequence.
SF is the user interface for the VIC. It can be iconified,
sized just for SF, or full debug/watch of various elements but
mostly watch, step, and edit of the current files used.
SF has options to step through the processing of script-file
lines and to limit processing. The ability to allow the user
to directly alter the line being processed and at the
different steps in the processing of the line. The user can
insert lines to be processed before and/or after the current
line and use SF in interactive mode (no SF-file being
processed). The option to send the line(s) to a file (tee)
with or (redirection) without sending it to the OP defined
device or program-port. All this can be done through PK
setting the SF-LPC (Line Processing Control) flags.
There is a keyboard key combination (Ctrl-P) to toggle step
and auto processing. It is also possible for a script-line
to select the processing mode, through a PK command call.
To properly understand the limitation of SF and PK abilities
to alter the sequence, understand that SF only processes the
current line for VIC variable and commands, optionally with
user interaction, before passing it on to the device or
program-port defined by OP. PK, in altering the SF stack only
alters the comming sequence of files and/or their next line
number(s) that SF processes.
SF is where the imagination process is set in motion. Also
where knowledge paths are mapped (tee/redirect output, with
comments, to file).
The SF-script file can be a pipe or port type of temporary
file. As is generated by IQ, ID, or external program (such as
another VIC or user interface). As well the tee/redirected to
file output can also be such a pipe or port type of temporary
file, or even a null device so that SF has no output.
"SF" files - The sequence files can be any script type files. Generally
these files contain commands for the VIC but may contain
lines for other programs. What is not completely process
by the VIC is passed on to the output as determined by "OP"
(which can be a shell the VIC is incorporated in.)
If incorporated into a shell, it is possible to tell SF not
to process a VIC command (say you want to use Csh "foreach"
to call a VIC command, you'd need a way to escape or pass
the VIC command pass SF.
SF
SF returns PK SF line
SF -? help on SF
SF -sf returns SF line contents
SF filename@line#... returns given filename@line# contents
------------------------------------------------------------------------
COPYRIGHT INFORMATION:
------------------------------------------------------------------------
Although this work is copyrighted, the intent of the copyright is to
support the concept of giving credit where credit is due and to prevent
the wrongful constraint and/or abuse/exploitation and/or distortion/
manipulation of it's content. This work may be transfer and used
following these conditions:
1) This work may be transferred only in whole and so long as NO
consideration is received in return.
2) That proper credit is given to the Author(s) responsible for the
creation of the work.
3) That there is no intentional distortion or manipulation of the work
that in any way damages or harms the work or authors(s) responsible
for the creation of the work. And that in finding any unintentional
distortions or manipulations, correction(s) will be made A.S.A.P. and
with reasonable effort to communicate the correction(s) to all.
4) This work shall not be included in any for-profit product and/or
service without the written approval of the authors(s) responsible
for it's creation. The exception to this is, of course relates to the
world wide web, in that the work may be made available on and through
the W.W.W. so long as the other conditions are adhered to.
****
Email: timrue@mindspring.com