Lit. Buffer overruns 1683

i've got an original, mint condition, v2.7.1 dated mar91 softcopy ... i think that I contributed to some website trying to collect complete history (as well as an autographed hard copy, also 1991).

another jargon file that may be of some interest was done originally by mike ... and a version can be found at

and a totally unrelated recent (mike) reference (and a PL where it is difficult to cause buffer overflows): which then leads to ansi standards

way back when i was redoing the system fault analysis program (previously mentioned in this thread, original was something like 60klocs of buttembler), i started out by saying that i would redo it in rex (before name change to rexx and released as product), make the rex version run ten times faster (than the buttembler version) and have ten times the functions (and initial version, start to finish-release in under six person weeks).

earlier posting in this thread random earlier postings

two related agendas was to 1) demonstrate power of rex ... and that it wasn't just another command scripting language like EXEC and EXEC2 ... and since this was getting into the transition period from full-source distribution and maintenance to object-code-only ... choose something (that at the time) would absolutely require source distribution (buttuming that they would ever decide to ship it to customers).

in another lifetime i went thru a period of appending random selected

entries to the end of email ... and then transitioned to yow-zippy.

I then tried to convert yow to support the jargon file. turns out that yow has a random number issue. zippy-yow file was around 30k bytes, and yow was using signed halfword random number (2**15-1) to select a byte location in the file ... and then do some twiddling to find a record (string) boundary. you could use yow on any file ... but it wouldn't work as might be expected with a file over 400kbytes.

Words of wisdom from Zippy: .. this must be what it's like to be a COLLEGE GRADUATE!!

and

IBM Jargon: MIP envy - n. The term, coined by Jim Gray in 1980, that began the Tandem Memos (q.v.). MIP envy is the coveting of other's facilities - not just the CPU power available to them, but also the languages, editors, debuggers, mail systems and networks. MIP envy is a term every programmer will understand, being another expression of the proverb The grbutt is always greener on the other side of the fence.

... and of course, i'm the one that has taken the blame for doing tandem memos (datamation even said so).

--