Talk:Print itself: Difference between revisions
Content added Content deleted
m (→Task appears to be redundant: added a comment.) |
(→Task appears to be redundant: Responded to Gerard.) |
||
| Line 4: | Line 4: | ||
: 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. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk:Gerard Schildberger|talk]]) 19:39, 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. -- [[User:Gerard Schildberger|Gerard Schildberger]] ([[User talk: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. --[[User:PureFox|PureFox]] ([[User talk:PureFox|talk]]) 20:38, 8 June 2020 (UTC) |
|||