SNOLIB(3)

πŸ“¦
version 2.3.1 Β· 3 versions
, in fedora 43, fedora 44, opensuse-leap 16.0

πŸ’– SNOLIB(3) πŸ’–

okay bestie, welcome to the CSNOBOL4 Manual page for snolib β€” yes that's the one, the SNOBOL4 library routines, and no I will not be normal about it πŸ’…


✨ NAME ✨

snolib β€” SNOBOL4 library routines. that's it. that's the whole name. iconic.


πŸŽ€ SYNOPSIS πŸŽ€

-INCLUDE 'filename.sno'

that's the whole vibe. you just -INCLUDE a file and boom, the routines are yours πŸ¦‹


🌸 DESCRIPTION 🌸

so here's the tea: the following snobol4(1) library routines are all available for -INCLUDE. like, every single one. let's go πŸ’–

  • bq.sno β€” runs a program in a subprocess and captures all the output, basically the shell/Perl backquote construct but make it SNOBOL4. yes queen, we're grabbing that stdout.
  • chars.sno β€” defines a variable for each non-printing character in the local character set. every invisible little guy gets a name 🫢
  • dynamic.sno β€” functions to compile and link dynamically LOADable extensions. snobol4ffi(3) does similar stuff but at run time, so pick your fighter ✨
  • ezio.sno β€” an alternative OPEN function, and the best part? no unit numbers needed. see snobol4ezio(3) for the whole story.
  • fence.sno, not.sno β€” emulation of SPITBOL FENCE() and NOT() functions, and we owe this one to Peter-Arno Coppen. king behavior πŸ‘‘
  • host.sno β€” function codes for the HOST() function, see snobol4host(3).
  • json.sno β€” functions to read/write a JSON subset, see snobol4json(3). yes bestie, SNOBOL4 does JSON, we stay versatile.
  • serv.sno β€” example TCP server program. a little demo server just for you 🧚
  • setup.sno β€” helper for building loadable modules, see snobol4setup(3).
  • smtp.sno β€” example code to send mail via TCP/SMTP. send the email, bestie πŸ’Œ
  • snobol4+.sno β€” SNOBOL4+ emulation functions: ENVIRONMENT(), EXECUTE(), TELL(), SEEK(). four of them. all yours.
  • spitbol.sno β€” SPITBOL I/O emulation functions (no unit numbers), specifically INPUT(), OUTPUT(), ENDFILE(), REWIND().
  • stcl.sno β€” prototypes and values for EXPERIMENTAL SNOBOL4 Tcl/Tk routines, see snobol4tcl(3). experimental, so like, be mindful πŸ”₯
  • tcp.sno β€” TCP connection routines, and they're used by the URL library right below πŸ‘‡
  • url.sno, file.sno, ftp.sno, http.sno β€” Internet URL file reading support, for file, ftp and http URL's. all the schemes, no cap.
  • utf.sno β€” experimental routines for handling UTF encoded (Unicode) data. again: experimental, so don't be shocked if it's giving chaos πŸ™ˆ
  • wrapper.sno β€” routines for creating C code wrappers for dynamically 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).

go read them. all of them. do it for me πŸ’œ


πŸ’« AUTHOR πŸ’«

Philip Budne Peter-Arno Coppen

absolute legends, we love them, we thank them 🌈


πŸ’€ BUGS πŸ’€

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

that's not me saying that, that's the man page saying that. and honestly? valid. every single -INCLUDE file deserves main character energy and its own page, fr fr 😭


and that's the whole page bestie, no notes ✨ this was CSNOBOL4B 2.3.1, dated March 31, 2022 β€” go forth and -INCLUDE responsibly πŸŽ€πŸ’–

πŸ“¦ where this page comes from