diff options
Diffstat (limited to 'doc/gawk.texi')
| -rw-r--r-- | doc/gawk.texi | 69 |
1 files changed, 45 insertions, 24 deletions
diff --git a/doc/gawk.texi b/doc/gawk.texi index 2da2a246..09700111 100644 --- a/doc/gawk.texi +++ b/doc/gawk.texi @@ -20,7 +20,7 @@ @c applies to and all the info about who's publishing this edition @c These apply across the board. -@set UPDATE-MONTH February, 2012 +@set UPDATE-MONTH October, 2012 @set VERSION 4.0 @set PATCHLEVEL 1 @@ -31880,6 +31880,50 @@ It was written in @command{awk} by Brian Kernighan and Jon Bentley, and is available from @uref{http://netlib.sandia.gov/netlib/typesetting/chem.gz}. +@cindex cookie +@item Cookie +A peculiar goodie, token, saying or remembrance +produced by or presented to a program. (With thanks to Doug McIlroy.) +@ignore +From: Doug McIlroy <doug@cs.dartmouth.edu> +Date: Sat, 13 Oct 2012 19:55:25 -0400 +To: arnold@skeeve.com +Subject: Re: origin of the term "cookie"? + +I believe the term "cookie", for a more or less inscrutable +saying or crumb of information, was injected into Unix +jargon by Bob Morris, who used the word quite frequently. +It had no fixed meaning as it now does in browsers. + +The word had been around long before it was recognized in +the 8th edition glossary (earlier editions had no glossary): + +cookie a peculiar goodie, token, saying or remembrance +returned by or presented to a program. [I would say that +"returned by" would better read "produced by", and assume +responsibility for the inexactitude.] + +Doug McIlroy + +From: Doug McIlroy <doug@cs.dartmouth.edu> +Date: Sun, 14 Oct 2012 10:08:43 -0400 +To: arnold@skeeve.com +Subject: Re: origin of the term "cookie"? + +> Can I forward your email to Eric Raymond, for possible addition to the +> Jargon File? + +Sure. I might add that I don't know how "cookie" entered Morris's +vocabulary. Certainly "values of beta give rise to dom!" (see google) +was an early, if not the earliest Unix cookie. The fact that it was +found lying around on a model 37 teletype (which had Greek beta in +its type box) suggests that maybe it was seen to be like milk and +cookies laid out for Santa Claus. Morris was wont to make such +connections. + +Doug +@end ignore + @item Coprocess A subordinate program with which two-way communications is possible. @@ -33664,9 +33708,6 @@ Unresolved Issues: of how to use them. It would be useful to perhaps have a "programming style" section of the manual that would include this and other tips. -2. The default AWKPATH search path should be configurable via `configure' - The default and how this changes needs to be documented. - Consistency issues: /.../ regexps are in @code, not @samp ".." strings are in @code, not @samp @@ -33765,23 +33806,3 @@ Suggestions: % 1. Standardize the error messages from the functions and programs % in Chapters 12 and 13. % 2. Nuke the BBS stuff and use something that won't be obsolete - -From: Doug McIlroy <doug@cs.dartmouth.edu> -Date: Sat, 13 Oct 2012 19:55:25 -0400 -To: arnold@skeeve.com -Subject: Re: origin of the term "cookie"? - -I believe the term "cookie", for a more or less inscrutable -saying or crumb of information, was injected into Unix -jargon by Bob Morris, who used the word quite frequently. -It had no fixed meaning as it now does in browsers. - -The word had been around long before it was recognized in -the 8th edition glossary (earlier editions had no glossary): - -cookie a peculiar goodie, token, saying or remembrance -returned by or presented to a program. [I would say that -"returned by" would better read "produced by", and assume -responsibility for the inexactitude.] - -Doug McIlroy |