Anonymous user
Talk:Quine: Difference between revisions
→origins of the word QUINE: added a new talk section.
(→origins of the word QUINE: added a new talk section.) |
|||
Line 128:
: I suspect that using <tt>sourceline()</tt> falls squarely into the category of "opening the source file of the program and similar mechanisms" which disqualifies it as a Quine. --[[User:Alansam|Alansam]] 06:05, 28 June 2012 (UTC)
:: I have a slightly different definition of squarely. The REXX program doesn't open the source file of the program. It doesn't read (or take) the source file through any other mechanism. Reading a copy of the file that is on (or in) a virtual device might be considered taking (reading?) a copy of the source. Putting a number of lines in a stack and then "reading" (or pulling) is "taking" some input could qualify as a method disallowed in the Wiki definition of a quine. I hesitate to call a stack (internal or external queue) a device,
== origins of the word ''quine'' ==
I first came across these thingys (quines) in 1967 or so ─── they weren't known as '''quines''' when I first encountered them, they were known simply as "reproduce (type/print) the (a) computer program language source to the console (terminal) or printer ─── or somesuch phraseology. I had never heard of a ''quine'' before I saw it mentioned here on Rosetta Code when this task was created. By the way, the word '''quine''' was introduced in 1979. Nor have I ever heard of another name for it: ''Computer Recreations: Self-Reproducing Automata'' (1972). Now that is a four-bit phrase. Other terms are ''self-replicating programs'', ''self-reproducing programs'', and ''self-copying programs''. I have adding these terms and others to the '''quine''' Rosetta Code task so as to make this task easier to find in case one doesn't know of the '''quine''' word or what it means. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 22:27, 8 June 2020 (UTC)
|