I'm working on modernizing Rosetta Code's infrastructure. Starting with communications. Please accept this time-limited open invite to RC's Slack.. --Michael Mol (talk) 20:59, 30 May 2020 (UTC)

Talk:Print itself

From Rosetta Code

Task appears to be redundant[edit]

It appears from the author's latest edit that what in fact is required here is a 'Quine'. As we already have a task for that (https://rosettacode.org/wiki/Quine), I suggest the author moves his Furor solutions over to that and I will delete mine. An administrator can then remove the draft task. --PureFox (talk) 18:32, 8 June 2020 (UTC)

Yes, I somewhat agree.   I had thought that the author was making a salient point about outputting the source of the program to the specifically mentioned   stdout   instead of just outputting the program's source (to the terminal, for instance).   If it does get removed, I'll update the Quine task to not include a Related task that points to this (draft) task.     -- Gerard Schildberger (talk) 19:39, 8 June 2020 (UTC)
I wasn't sure what to make of it at first. There was nothing to suggest it was a Quine (though I don't understand the Furor code) and there would have been no point in creating another Quine task anyway. I therefore assumed it was just asking for a solution which read the source code somehow and posted code accordingly. There may be some compiled languages which have a problem identifying what their source file is called (though not Go) and so, even if this is all the task were about, it did not seem completely pointless. --PureFox (talk) 20:38, 8 June 2020 (UTC)
Hi everybody, I'm very sorry! This is obviously my error! PureFox was quite right. I did not know anything about that abovementioned "Quine" task at all, excuse me! But now I moved my Furor solution over to that. However I do not think it would be necessary to delete this page. I've erased the additional-inserted sentence from the description, and created a small Furor program based on similar idea than that of PureFox's. Violazoli (talk) 21:00, 8 June 2020 (UTC)
Hi and welcome to RC. With 1200+ tasks on RC nowadays, I know it can be difficult to figure out what's been done before so no worries there :) Happy to let the task stand on the present basis now. --PureFox (talk) 21:18, 8 June 2020 (UTC)
I first came across these thingys in 1967 --- they weren't known as quines when I first encountered them,   they were known simply as "reproduce (type/print) the computer program 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 the 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 will be adding these terms and others to the quine Rosetta Code task so as to make that task easier to find in case one doesn't know of the quine word or what it means.     -- Gerard Schildberger (talk) 21:48, 8 June 2020 (UTC)