REPL

docs/jargon-org.txt

@@ -19,7 +19,7 @@ Free Documentation License".
 
 * Generated
 
-This file last generated Friday, 19 October 2018 11:37AM UTC
+This file last generated Sunday, 11 November 2018 09:19PM UTC
 
 * Glossary
 ** (
@@ -1323,6 +1323,9 @@ interj. [Named for Captain Gym Z. Quirk, the first to raise it.] Objection! Assu
 *** README file
 n. Hacker's-eye introduction traditionally included in the top-level directory of a Unix source distribution, containing a pointer to more detailed documentation, credits, miscellaneous revision history, notes, etc. In the Mac and PC worlds, software is not usually distributed in source form, and the README is more likely to contain user-oriented material like last-minute documentation changes, error workarounds, and restrictions. When asked, hackers invariably relate the README convention to the famous scene in Lewis Carroll's Alice's Adventures In Wonderland in which Alice confronts magic munchies labeled Eat Me and Drink Me. The file may be named README, or READ.ME, or rarely ReadMe or readme.txt or some other variant. The all-upper-case spellings, however, are universal among Unix programmers. By ancient tradition, real source files have all-lowercase names and all-uppercase is reserved for metadata, comments, and grafitti. This is functional; because 'A' sorts before 'a' in ASCII, the README will appear in directory listings before any source file.
 
+*** REPL
+acronym for Read–Eval–Print Loop, otherwise known as an interactive command shell.
+
 *** RETI
 v. Syn.
 
@@ -2057,9 +2060,6 @@ n. [Commodore users; perh. a deliberate phonetic mangling of boolean variable ?]
 
 4. Used by MUDders on occasion in a more general sense related to sense 3, to refer to directing someone to another location or resource (eg. A user was asking about XYZ so I bamfed them to https://zombo.com)
 
-*** banana principle
-Also known as "perpetual beta", "git versioning" or never setting an official release date. Where you ship your software early as an alpha or beta and just keep upgrading it straight from the source repository instead of doing releases with version numbers on predefined dates. It comes from a marketing term which is an analogy to how bananas are picked while they're still unripe and shipped in that condition. An early example of this was Gmail, which remained in beta for years while also being a live production system with many users.
-
 *** banana problem
 n. [from the story of the little girl who said I know how to spell banana , but I don't know when to stop ]. Not knowing where or when to bring a production to a close (compare fencepost error ). One may say there is a banana problem of an algorithm with poorly defined or incorrect termination conditions, or in discussing the evolution of a design that may be succumbing to featuritis (see also creeping elegance , creeping featuritis ). See item 176 under HAKMEM , which describes a banana problem in a Dissociated Press implementation. Also, see one-banana problem for a superficially similar but unrelated usage.
 

docs/jargon.html

@@ -18,7 +18,7 @@ Free Documentation License".
       </p>
       <H2>Generated</H2>
       <p>
-This file last generated Friday, 19 October 2018 11:37AM UTC
+This file last generated Sunday, 11 November 2018 09:19PM UTC
 
       </p>
       <H2>Glossary</H2>
@@ -1623,6 +1623,10 @@ This file last generated Friday, 19 October 2018 11:37AM UTC
         <p>
         n. Hacker's-eye introduction traditionally included in the top-level directory of a Unix source distribution, containing a pointer to more detailed documentation, credits, miscellaneous revision history, notes, etc. In the Mac and PC worlds, software is not usually distributed in source form, and the README is more likely to contain user-oriented material like last-minute documentation changes, error workarounds, and restrictions. When asked, hackers invariably relate the README convention to the famous scene in Lewis Carroll's Alice's Adventures In Wonderland in which Alice confronts magic munchies labeled Eat Me and Drink Me. The file may be named README, or READ.ME, or rarely ReadMe or readme.txt or some other variant. The all-upper-case spellings, however, are universal among Unix programmers. By ancient tradition, real source files have all-lowercase names and all-uppercase is reserved for metadata, comments, and grafitti. This is functional; because 'A' sorts before 'a' in ASCII, the README will appear in directory listings before any source file.
         </p>
+        <H4>REPL</H4>
+        <p>
+        acronym for Read–Eval–Print Loop, otherwise known as an interactive command shell.
+        </p>
         <H4>RETI</H4>
         <p>
         v. Syn.
@@ -2500,10 +2504,6 @@ This file last generated Friday, 19 October 2018 11:37AM UTC
 <p>3. In MUD circles, bamf is also used to refer to the act by which a MUD server sends a special notification to the MUD client to switch its connection to another server ( I'll set up the old site to just bamf people over to our new location. ). </p>
 
 <p>4. Used by MUDders on occasion in a more general sense related to sense 3, to refer to directing someone to another location or resource (eg. A user was asking about XYZ so I bamfed them to https://zombo.com)</p>
-        <H4>banana principle</H4>
-        <p>
-        Also known as "perpetual beta", "git versioning" or never setting an official release date. Where you ship your software early as an alpha or beta and just keep upgrading it straight from the source repository instead of doing releases with version numbers on predefined dates. It comes from a marketing term which is an analogy to how bananas are picked while they're still unripe and shipped in that condition. An early example of this was Gmail, which remained in beta for years while also being a live production system with many users.
-        </p>
         <H4>banana problem</H4>
         <p>
         n. [from the story of the little girl who said I know how to spell banana , but I don't know when to stop ]. Not knowing where or when to bring a production to a close (compare fencepost error ). One may say there is a banana problem of an algorithm with poorly defined or incorrect termination conditions, or in discussing the evolution of a design that may be succumbing to featuritis (see also creeping elegance , creeping featuritis ). See item 176 under HAKMEM , which describes a banana problem in a Dissociated Press implementation. Also, see one-banana problem for a superficially similar but unrelated usage.

entries/REPL.txt

@@ -0,0 +1,4 @@
+REPL
+
+acronym for Read–Eval–Print Loop, otherwise known as an interactive command
+shell.