SNOLIB(3)

NAME
snolib - SNOBOL4 library routines

SYNOPSIS
-INCLUDE 'filename.sno'

DESCRIPTION
The following snobol4(1) library routines are available for -INCLUDE:

bq.sno
    run a program in a subprocess and capture all output, like shell/Perl backquote construct.

chars.sno
    defines a variable for each non-printing character in the local character set.

dynamic.sno
    functions to compile and link dynamicly LOADable extensions. snobol4ffi(3) provides similar functionality at run time.

ezio.sno
    Alternative OPEN function, without the need for unit numbers, see snobol4ezio(3).

fence.sno, not.sno
    Emulation of SPITBOL FENCE() and NOT() functions thanks to Peter-Arno Coppen.

host.sno
    Function codes for HOST() function, see snobol4host(3).

json.sno
    Functions to read/write JSON subset, see snobol4json(3).

serv.sno
    Example TCP server program.

setup.sno
    Helper for building loadable modules, see snobol4setup(3).

smtp.sno
    Example code to send mail via TCP/SMTP.

snobol4+.sno
    SNOBOL4+ emulation functions: ENVIRONMENT(), EXECUTE(), TELL(), SEEK().

spitbol.sno
    SPITBOL I/O emulation functions (no unit numbers) INPUT(), OUTPUT(), ENDFILE(), REWIND().

stcl.sno
    Prototypes and values for EXPERIMENTAL SNOBOL4 Tcl/Tk routines, see snobol4tcl(3).

tcp.sno
    TCP connection routines, used by the URL library (below)

url.sno, file.sno, ftp.sno, http.sno
    Internet URL file reading support (for file, ftp and http URL's).

utf.sno
    Experimental routines for handling UTF encoded (Unicode) data.

wrapper.sno
    Routines for creating C code wrappers for dynamicly loading code.

SEE ALSO
snobol4(1), snobol4base64(3), snobol4digest(3), snobol4dirs(3), snobol4ezio(3), snobol4ffi(3), snobol4fork(3), snobol4host(3), snobol4json(3), snobol4logic(3), snobol4ndbm(3), snobol4random(3), snobol4readline(3), snobol4setup(3), snobol4sprintf(3), snobol4sqlite3(3), snobol4stat(3), snobol4stcl(3), snobol4time(3), snobol4zlib(3).

AUTHOR
Philip Budne
Peter-Arno Coppen

BUGS
Each include file should have it's own man page!