Talk:208: Regular Expressions - Revision history

172.70.160.249 at 11:12, 1 August 2024

2024-08-01T11:12:56Z

172.68.210.117: Added a comment about the hover text being unexplained since RegEx doesn't need spaces to be escaped.

2024-08-01T01:07:57Z

Added a comment about the hover text being unexplained since RegEx doesn't need spaces to be escaped.

173.245.52.116 at 20:18, 26 November 2016

2016-11-26T20:18:53Z

108.162.250.162 at 06:47, 30 June 2015

2015-06-30T06:47:05Z

Zetfr at 09:55, 20 May 2015

2015-05-20T09:55:52Z

197.234.242.240: Find implies physical address

2015-01-30T14:48:48Z

Find implies physical address

173.245.56.189 at 00:52, 30 January 2015

2015-01-30T00:52:30Z

108.162.246.117 at 05:41, 1 November 2013

2013-11-01T05:41:21Z

178.98.31.27 at 00:00, 22 June 2013

2013-06-22T00:00:46Z

Davidy22 at 23:26, 29 November 2012

2012-11-29T23:26:47Z

← Older revision		Revision as of 11:12, 1 August 2024
Line 16:		Line 16:

	"Forgot to escape a space" in the hover text should also be explained, because spaces don't ever need to be escaped in RegEx as they aren't special characters, so that's either a mistake or another layer of the joke. [[Special:Contributions/172.68.210.117\|172.68.210.117]] 01:07, 1 August 2024 (UTC)		"Forgot to escape a space" in the hover text should also be explained, because spaces don't ever need to be escaped in RegEx as they aren't special characters, so that's either a mistake or another layer of the joke. [[Special:Contributions/172.68.210.117\|172.68.210.117]] 01:07, 1 August 2024 (UTC)
		+	:Given that it is Perl, he may indeed need to escape intended spaces, due to taking advantage of the use of [https://perldoc.perl.org/perlre#%2Fx-and-%2Fxx /x or /xx options being used]. It's something I rarely do myself, but perhaps I should (for readability, etc).
		+	:Alternately, he's put in one or more "/s" (any whitespace character) only as "s" (the literal character 's') in his original hasty typing, but the former sounds more likely. [[Special:Contributions/172.70.160.249\|172.70.160.249]] 11:12, 1 August 2024 (UTC)

← Older revision		Revision as of 01:07, 1 August 2024
Line 14:		Line 14:

	This is probably how they wrote Encyclopedia Brown. --[[Special:Contributions/173.245.52.116\|173.245.52.116]] 20:18, 26 November 2016 (UTC)		This is probably how they wrote Encyclopedia Brown. --[[Special:Contributions/173.245.52.116\|173.245.52.116]] 20:18, 26 November 2016 (UTC)
		+
		+	"Forgot to escape a space" in the hover text should also be explained, because spaces don't ever need to be escaped in RegEx as they aren't special characters, so that's either a mistake or another layer of the joke. [[Special:Contributions/172.68.210.117\|172.68.210.117]] 01:07, 1 August 2024 (UTC)

← Older revision		Revision as of 20:18, 26 November 2016
Line 12:		Line 12:

	It's kinda funny that people are taking this so seriously when the comic itself (and the fact that it's in a comic) establishes this as a fantastical scenario. -Pennpenn [[Special:Contributions/108.162.250.162\|108.162.250.162]] 06:47, 30 June 2015 (UTC)		It's kinda funny that people are taking this so seriously when the comic itself (and the fact that it's in a comic) establishes this as a fantastical scenario. -Pennpenn [[Special:Contributions/108.162.250.162\|108.162.250.162]] 06:47, 30 June 2015 (UTC)
		+
		+	This is probably how they wrote Encyclopedia Brown. --[[Special:Contributions/173.245.52.116\|173.245.52.116]] 20:18, 26 November 2016 (UTC)

← Older revision		Revision as of 06:47, 30 June 2015
Line 10:		Line 10:
	The explanation misses the main point of the comic: a regex expert is so efficient he can solve a hard problem in a split second. Assuming, for instance, he jumped from 2 m high and he can type while he is less than 50 cm from the keyboard, he would have about .15 second to type. There's no way he could enter a long program implementing a complex algorithm but, according to Randall, this is sufficient to enter a compact regex that solves the problem.		The explanation misses the main point of the comic: a regex expert is so efficient he can solve a hard problem in a split second. Assuming, for instance, he jumped from 2 m high and he can type while he is less than 50 cm from the keyboard, he would have about .15 second to type. There's no way he could enter a long program implementing a complex algorithm but, according to Randall, this is sufficient to enter a compact regex that solves the problem.
	In the title text, he is swinging back like a pendulum and using his new split-second typing opportunity to fix a bug in his initial regex. Zetfr 09:55, 20 May 2015 (UTC)		In the title text, he is swinging back like a pendulum and using his new split-second typing opportunity to fix a bug in his initial regex. Zetfr 09:55, 20 May 2015 (UTC)
		+
		+	It's kinda funny that people are taking this so seriously when the comic itself (and the fact that it's in a comic) establishes this as a fantastical scenario. -Pennpenn [[Special:Contributions/108.162.250.162\|108.162.250.162]] 06:47, 30 June 2015 (UTC)

← Older revision		Revision as of 09:55, 20 May 2015
Line 7:		Line 7:
	:It's an EMAIL address they're trying to match. Not quite obvious if you're not already thinking emails. At the same time, you COULD most likely catch a lot of the most common street address types, like 1234 Name Rd/St/Ave/etc. [[Special:Contributions/173.245.56.189\|173.245.56.189]] 00:52, 30 January 2015 (UTC)		:It's an EMAIL address they're trying to match. Not quite obvious if you're not already thinking emails. At the same time, you COULD most likely catch a lot of the most common street address types, like 1234 Name Rd/St/Ave/etc. [[Special:Contributions/173.245.56.189\|173.245.56.189]] 00:52, 30 January 2015 (UTC)
	::No. "But to find them we'd need to search through 200MB of emails looking for something formatted like an address!" To '''find''' someone you need a physical address, not an email address. --[[Special:Contributions/197.234.242.240\|197.234.242.240]] 14:48, 30 January 2015 (UTC)		::No. "But to find them we'd need to search through 200MB of emails looking for something formatted like an address!" To '''find''' someone you need a physical address, not an email address. --[[Special:Contributions/197.234.242.240\|197.234.242.240]] 14:48, 30 January 2015 (UTC)
		+
		+	The explanation misses the main point of the comic: a regex expert is so efficient he can solve a hard problem in a split second. Assuming, for instance, he jumped from 2 m high and he can type while he is less than 50 cm from the keyboard, he would have about .15 second to type. There's no way he could enter a long program implementing a complex algorithm but, according to Randall, this is sufficient to enter a compact regex that solves the problem.
		+	In the title text, he is swinging back like a pendulum and using his new split-second typing opportunity to fix a bug in his initial regex. Zetfr 09:55, 20 May 2015 (UTC)

← Older revision		Revision as of 14:48, 30 January 2015
Line 6:		Line 6:
	I don't think a regex can isolate an address, it has so many forms that it can not be considered regular language. This discussion comes to similar conclusions: http://stackoverflow.com/questions/9397485/regex-street-address-match [[Special:Contributions/108.162.246.117\|108.162.246.117]] 05:41, 1 November 2013 (UTC)		I don't think a regex can isolate an address, it has so many forms that it can not be considered regular language. This discussion comes to similar conclusions: http://stackoverflow.com/questions/9397485/regex-street-address-match [[Special:Contributions/108.162.246.117\|108.162.246.117]] 05:41, 1 November 2013 (UTC)
	:It's an EMAIL address they're trying to match. Not quite obvious if you're not already thinking emails. At the same time, you COULD most likely catch a lot of the most common street address types, like 1234 Name Rd/St/Ave/etc. [[Special:Contributions/173.245.56.189\|173.245.56.189]] 00:52, 30 January 2015 (UTC)		:It's an EMAIL address they're trying to match. Not quite obvious if you're not already thinking emails. At the same time, you COULD most likely catch a lot of the most common street address types, like 1234 Name Rd/St/Ave/etc. [[Special:Contributions/173.245.56.189\|173.245.56.189]] 00:52, 30 January 2015 (UTC)
		+	::No. "But to find them we'd need to search through 200MB of emails looking for something formatted like an address!" To '''find''' someone you need a physical address, not an email address. --[[Special:Contributions/197.234.242.240\|197.234.242.240]] 14:48, 30 January 2015 (UTC)

← Older revision		Revision as of 00:52, 30 January 2015
Line 5:		Line 5:

	I don't think a regex can isolate an address, it has so many forms that it can not be considered regular language. This discussion comes to similar conclusions: http://stackoverflow.com/questions/9397485/regex-street-address-match [[Special:Contributions/108.162.246.117\|108.162.246.117]] 05:41, 1 November 2013 (UTC)		I don't think a regex can isolate an address, it has so many forms that it can not be considered regular language. This discussion comes to similar conclusions: http://stackoverflow.com/questions/9397485/regex-street-address-match [[Special:Contributions/108.162.246.117\|108.162.246.117]] 05:41, 1 November 2013 (UTC)
		+	:It's an EMAIL address they're trying to match. Not quite obvious if you're not already thinking emails. At the same time, you COULD most likely catch a lot of the most common street address types, like 1234 Name Rd/St/Ave/etc. [[Special:Contributions/173.245.56.189\|173.245.56.189]] 00:52, 30 January 2015 (UTC)

← Older revision		Revision as of 05:41, 1 November 2013
Line 3:		Line 3:

	<nowiki></nowiki>Grumble grumble, email should be intrinsically treated as 7-bit ASCII. 200MB of email would be almost 210 million bytes, raw. Even assuming half of that is header overheads on top of a whole lot of short message bodies, that's a lot more characters still to processed than 5 million. Of course, if people send more complex data through common MIME extensions (or the old favourites of uuencoding, etc) so as to send extended characters and binary-attachments (including various compressed formats of data, but again needing significant overheads when not containing large documents within), then that reduces the amount of characters needing searching (but probably needs a few more "use <foo>::<bar>;" bits on your Perl code, in order to give you the tools to isolate such blocks and decode what's in them for further searching within). But things went downhill ever since people could start sending emails with fancy graphical signatures and backgrounds... Yeah, I'm an Old Fogey from the dark ages. [[Special:Contributions/178.98.31.27\|178.98.31.27]] 00:00, 22 June 2013 (UTC)		<nowiki></nowiki>Grumble grumble, email should be intrinsically treated as 7-bit ASCII. 200MB of email would be almost 210 million bytes, raw. Even assuming half of that is header overheads on top of a whole lot of short message bodies, that's a lot more characters still to processed than 5 million. Of course, if people send more complex data through common MIME extensions (or the old favourites of uuencoding, etc) so as to send extended characters and binary-attachments (including various compressed formats of data, but again needing significant overheads when not containing large documents within), then that reduces the amount of characters needing searching (but probably needs a few more "use <foo>::<bar>;" bits on your Perl code, in order to give you the tools to isolate such blocks and decode what's in them for further searching within). But things went downhill ever since people could start sending emails with fancy graphical signatures and backgrounds... Yeah, I'm an Old Fogey from the dark ages. [[Special:Contributions/178.98.31.27\|178.98.31.27]] 00:00, 22 June 2013 (UTC)
		+
		+	I don't think a regex can isolate an address, it has so many forms that it can not be considered regular language. This discussion comes to similar conclusions: http://stackoverflow.com/questions/9397485/regex-street-address-match [[Special:Contributions/108.162.246.117\|108.162.246.117]] 05:41, 1 November 2013 (UTC)

← Older revision		Revision as of 00:00, 22 June 2013
Line 1:		Line 1:
	Hi, sorry about the previous "poor explanation". This one is pretty straight-forward (I think), given enough information about "regex"es and Perl. On a side-note, how did you find out the date for the comic? -- NariOx		Hi, sorry about the previous "poor explanation". This one is pretty straight-forward (I think), given enough information about "regex"es and Perl. On a side-note, how did you find out the date for the comic? -- NariOx
	:The explanation was mostly accurate, my gripe was with the fact that a number of fields were empty - the transcript, date and categories weren't done. You can find the date in the "all comics" page, accessible from the sidebar. [[User:Davidy22\|<span title="I want you."><u><font color="purple" size="2px">David</font><font color="green" size="3px">y</font></u><sup><font color="indigo" size="1px">22</font></sup></span>]][[User talk:Davidy22\|<tt>[talk]</tt>]] 23:26, 29 November 2012 (UTC)		:The explanation was mostly accurate, my gripe was with the fact that a number of fields were empty - the transcript, date and categories weren't done. You can find the date in the "all comics" page, accessible from the sidebar. [[User:Davidy22\|<span title="I want you."><u><font color="purple" size="2px">David</font><font color="green" size="3px">y</font></u><sup><font color="indigo" size="1px">22</font></sup></span>]][[User talk:Davidy22\|<tt>[talk]</tt>]] 23:26, 29 November 2012 (UTC)
		+
		+	<nowiki></nowiki>Grumble grumble, email should be intrinsically treated as 7-bit ASCII. 200MB of email would be almost 210 million bytes, raw. Even assuming half of that is header overheads on top of a whole lot of short message bodies, that's a lot more characters still to processed than 5 million. Of course, if people send more complex data through common MIME extensions (or the old favourites of uuencoding, etc) so as to send extended characters and binary-attachments (including various compressed formats of data, but again needing significant overheads when not containing large documents within), then that reduces the amount of characters needing searching (but probably needs a few more "use <foo>::<bar>;" bits on your Perl code, in order to give you the tools to isolate such blocks and decode what's in them for further searching within). But things went downhill ever since people could start sending emails with fancy graphical signatures and backgrounds... Yeah, I'm an Old Fogey from the dark ages. [[Special:Contributions/178.98.31.27\|178.98.31.27]] 00:00, 22 June 2013 (UTC)

← Older revision		Revision as of 23:26, 29 November 2012
Line 1:		Line 1:
	Hi, sorry about the previous "poor explanation". This one is pretty straight-forward (I think), given enough information about "regex"es and Perl. On a side-note, how did you find out the date for the comic? -- NariOx		Hi, sorry about the previous "poor explanation". This one is pretty straight-forward (I think), given enough information about "regex"es and Perl. On a side-note, how did you find out the date for the comic? -- NariOx
		+	:The explanation was mostly accurate, my gripe was with the fact that a number of fields were empty - the transcript, date and categories weren't done. You can find the date in the "all comics" page, accessible from the sidebar. [[User:Davidy22\|<span title="I want you."><u><font color="purple" size="2px">David</font><font color="green" size="3px">y</font></u><sup><font color="indigo" size="1px">22</font></sup></span>]][[User talk:Davidy22\|<tt>[talk]</tt>]] 23:26, 29 November 2012 (UTC)