Editing Talk:1685: Patch
Please sign your posts with ~~~~ |
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 1: | Line 1: | ||
<!--Please sign your posts with ~~~~--> | <!--Please sign your posts with ~~~~--> | ||
− | Hey, I'm first! Guessing the Bot only JUST created this, it was mere minutes after midnight EST when I landed on this page. Unfortunately this is a comic I'm less capable of explaining. From the looks of it, his Photoshop Patch turned what looks like C code into gobbledegook by filling in several of the spaces (and I think even changing some of the characters, possible with characters which fill more of the space). - NiceGuy1 [[Special:Contributions/108.162.218.77|108.162.218.77]] 04:24, 25 May 2016 | + | Hey, I'm first! Guessing the Bot only JUST created this, it was mere minutes after midnight EST when I landed on this page. Unfortunately this is a comic I'm less capable of explaining. From the looks of it, his Photoshop Patch turned what looks like C code into gobbledegook by filling in several of the spaces (and I think even changing some of the characters, possible with characters which fill more of the space). - NiceGuy1 [[Special:Contributions/108.162.218.77|108.162.218.77]] 04:24, 25 May 2016 (UTC) |
This appears to be Python code. Note the "def" keyword, how "for i in [garbled]:" is used rather than C's for syntax, and how there are no semicolons or braces. --[[User:Sherlock9|Sherlock9]] ([[User talk:Sherlock9|talk]]) 05:03, 25 May 2016 (UTC) | This appears to be Python code. Note the "def" keyword, how "for i in [garbled]:" is used rather than C's for syntax, and how there are no semicolons or braces. --[[User:Sherlock9|Sherlock9]] ([[User talk:Sherlock9|talk]]) 05:03, 25 May 2016 (UTC) | ||
Line 34: | Line 34: | ||
It might be worth explaining the [pivot] * (len(a) - (len(l) + len(r))) since that threw me when I first saw it. Since l has the elements of a < pivot, and r has the elements of a > pivot, len(a) - (len(l) + len(r)) will be the number of elements in a that = pivot (which must be in the range [1, len(a)]), and these are then 'spliced' into the result between the result of quicksorting l and r. | It might be worth explaining the [pivot] * (len(a) - (len(l) + len(r))) since that threw me when I first saw it. Since l has the elements of a < pivot, and r has the elements of a > pivot, len(a) - (len(l) + len(r)) will be the number of elements in a that = pivot (which must be in the range [1, len(a)]), and these are then 'spliced' into the result between the result of quicksorting l and r. | ||
[[User:Jstout|Jstout]] ([[User talk:Jstout|talk]]) 19:48, 26 May 2016 (UTC) | [[User:Jstout|Jstout]] ([[User talk:Jstout|talk]]) 19:48, 26 May 2016 (UTC) | ||
− | |||
− | |||
;Resemblance to Xerox number mangling issue | ;Resemblance to Xerox number mangling issue | ||
Line 45: | Line 43: | ||
:A couple of decades ago, the firm I was working for suddenly realised that one of its dot-matrix printers was causing problems. It was being used to print out specific validation information for archival, but the centre pin of the (vertical)print-head pin array was no longer striking. Out of 9 or perhaps 13 pins, it didn't represent much difference in the output ''normally'', but the difference between a 0 and a 8 was whether that pin's contribution was two separated pixels, the middle of the two long verticals in the zero*, or a short horizontal sequence of dots representing the contact between the two small circles in the eight. The way the hardly-noticed absent row caused the character to be read meant that both read as zero, with no difference. (Other characters had problems, but usually did not look like anything else. There were no hyphens/minus-signs, but they might have rendered as whitespace if there had been.) This was not an ideal situation, and a different printer was swapped in ASAP. | :A couple of decades ago, the firm I was working for suddenly realised that one of its dot-matrix printers was causing problems. It was being used to print out specific validation information for archival, but the centre pin of the (vertical)print-head pin array was no longer striking. Out of 9 or perhaps 13 pins, it didn't represent much difference in the output ''normally'', but the difference between a 0 and a 8 was whether that pin's contribution was two separated pixels, the middle of the two long verticals in the zero*, or a short horizontal sequence of dots representing the contact between the two small circles in the eight. The way the hardly-noticed absent row caused the character to be read meant that both read as zero, with no difference. (Other characters had problems, but usually did not look like anything else. There were no hyphens/minus-signs, but they might have rendered as whitespace if there had been.) This was not an ideal situation, and a different printer was swapped in ASAP. | ||
: * - This typeface's zero did not have a diagonal bar, of the type I even habitually ''handwrite'', but confusion with O-for-Oscar characters was already not an issue due to context... [[Special:Contributions/141.101.98.43|141.101.98.43]] 03:37, 27 May 2016 (UTC) | : * - This typeface's zero did not have a diagonal bar, of the type I even habitually ''handwrite'', but confusion with O-for-Oscar characters was already not an issue due to context... [[Special:Contributions/141.101.98.43|141.101.98.43]] 03:37, 27 May 2016 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− |