PATH and 10 Print Interpretation
From Maze
(Difference between revisions)
(→Discussion) | (→Discussion) | ||
| Line 65: | Line 65: | ||
Ian: Except not really, because the output of 10 print is NOT / and \ but PETSCII characters that look similar to those but which are different. Just sayin. | Ian: Except not really, because the output of 10 print is NOT / and \ but PETSCII characters that look similar to those but which are different. Just sayin. | ||
| − | Nick: Right, but as I noted earlier, it's a Path program where <pre>Path' [Path-prime]</pre> is a modified version of Path that prepends $ to a program automatically before | + | Nick: Right, but as I noted earlier, it's a Path program where <nowiki>Path' [Path-prime]</nowiki> is a modified version of Path that prepends $ to a program automatically before |
processing it and uses PETSCII 109 and 110 instead of / and \. | processing it and uses PETSCII 109 and 110 instead of / and \. | ||
| − | Jeremy: A succinct recap: 10 print outputs executable <pre>Path'</pre> programs, whose operations are a kind of performance of the maze-like wandering that we see implicit in 10 print. This is one response to the argument that 10 print does not informatically specify a maze-like texture, with a demonstration being that replacing the PETSCII characters with Ps and Qs, causing our perception of it to suddenly change. <pre>Path'</pre> retorts that it threads the labyrinth of Ps and Qs all the same. What I love about Michael's Path version of 10 print is that it closes the loop -- it isn't a quine, or elegant in the way that a one-liner is elegant, but instead it uses a program in which characters that are visual metaphors are executed to specify output that are in turn a texture of similar visual metaphors, which are in turn executable. | + | Jeremy: A succinct recap: 10 print outputs executable <nowiki>Path'</nowiki> programs, whose operations are a kind of performance of the maze-like wandering that we see implicit in 10 print. This is one response to the argument that 10 print does not informatically specify a maze-like texture, with a demonstration being that replacing the PETSCII characters with Ps and Qs, causing our perception of it to suddenly change. <nowiki>Path'</nowiki> retorts that it threads the labyrinth of Ps and Qs all the same. What I love about Michael's Path version of 10 print is that it closes the loop -- it isn't a quine, or elegant in the way that a one-liner is elegant, but instead it uses a program in which characters that are visual metaphors are executed to specify output that are in turn a texture of similar visual metaphors, which are in turn executable. |
== PATH Prime == | == PATH Prime == | ||
