Editing 859: (
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 4: | Line 4: | ||
| title = ( | | title = ( | ||
| image = (.png | | image = (.png | ||
− | | titletext = Brains aside, I wonder how many poorly-written xkcd.com-parsing scripts will break on this title (or ;;"'<nowiki/>'{<<[' this mouseover text." | + | | titletext = Brains aside, I wonder how many poorly-written xkcd.com-parsing scripts will break on this title (or ;;"'<nowiki />'{<<[' this mouseover text." |
+ | | imagesize = | ||
}} | }} | ||
== Explanation == | == Explanation == | ||
+ | In programming, punctuation is often used to mark sections of code. Paired punctuation marks must always be matched up with a corresponding closing mark, otherwise a so-called {{w|Syntax error|syntax error}} occurs. The programming language {{w|Lisp_(programming_language)|Lisp}} (also featured in [[224: Lisp]]) is known for large numbers of nested/paired parentheses. Even in literary works intended only for human consumption, the absence of a matching closing parenthesis, (as appears in this paragraph) or other "balanced" punctuation sets creates a mental expectation of eventual closure and completion that remains unfulfilled even long after the unmatched mark is encountered. | ||
− | + | There is also reference to [[312: With Apologies to Robert Frost]] which could contain the missing paren... | |
− | |||
− | |||
− | |||
− | There is also | ||
It can also be interpreted as a {{w|metaphor}}, which compares the reader with a Lisp {{w|Interpreter (Computing)|interpreter}}. The interpreter looks for the parenthesis until the end of the file, where it eventually halts, and prints out the error. The comic claims that if you read an unmatched parenthesis, you will look for it for the rest of the day too. | It can also be interpreted as a {{w|metaphor}}, which compares the reader with a Lisp {{w|Interpreter (Computing)|interpreter}}. The interpreter looks for the parenthesis until the end of the file, where it eventually halts, and prints out the error. The comic claims that if you read an unmatched parenthesis, you will look for it for the rest of the day too. | ||
− | It also refers to | + | It also refers to this awkward feeling when you see something (like an unmatched parentheses, speeling<!--sic--> error or a randomly-placed, comma. |
− | |||
− | |||
− | |||
− | |||
− | The title text refers to the same issue as already highlighted in [[327: Exploits of a Mom]]: if your scripts trust external input, you sometimes will be surprised. At the time of this comic, there were quite a few websites that would grab the | + | ===Title text=== |
+ | The title text refers to the same issue as already highlighted in [[327: Exploits of a Mom]]: if your scripts trust external input, you sometimes will be surprised. At the time of this comic, there were quite a few websites that would grab the latest xkcd comic three times a week and publish them on their own site. This comic likely broke at least some of the websites because of either the unmatched brace or the extra unmatched markup that is in the title text. | ||
==Transcript== | ==Transcript== | ||
− | + | (An unmatched left parenthesis creates an unresolved tension that will stay with you all day. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
{{comic discussion}} | {{comic discussion}} | ||
+ | <!-- [[Category:Out of the Ordinary]] ?--> | ||
[[Category:Programming]] | [[Category:Programming]] |