|
tripwire posted:There is no god I think it's more proof that the designers of RFC 822 were not very forward-thinking when they came up with it.
|
# ? Feb 12, 2009 04:51 |
|
|
# ? Apr 29, 2024 08:31 |
|
TRex EaterofCars posted:I think it's more proof that the designers of RFC 822 were not very forward-thinking when they came up with it. Or that they expected you to write a simple parser instead of using a regex.
|
# ? Feb 12, 2009 05:08 |
|
Erasmus Darwin posted:
A coworker stumbled across this and forwarded it to me: code:
|
# ? Feb 12, 2009 06:25 |
|
Avenging Dentist posted:Or that they expected you to write a simple parser instead of using a regex. Considering that email addresses can contain nested comments, the authors were simply masochistic. But really, use something like "does the string contain a @" as basic validation to make sure the user didn't mess up, then validate by actually sending mail.
|
# ? Feb 12, 2009 06:36 |
|
A copy of that regex takes about 2MB of RAM and 2 ms to compile into an internal FSM representation on my computer.
|
# ? Feb 12, 2009 06:53 |
|
ehnus posted:A coworker stumbled across this and forwarded it to me: But a switch statement won't work with booleans, so how else would you be able to select the value to return
|
# ? Feb 12, 2009 08:52 |
|
Janin posted:.+@.+ amivalid@123.23.3
|
# ? Feb 12, 2009 12:41 |
|
ehnus posted:A coworker stumbled across this and forwarded it to me: code:
|
# ? Feb 12, 2009 12:44 |
|
Zombywuf posted:
Honestly, given the number of email validators I've come across that incorrectly tell me that my email is invalid because it's got a '+' in it, I'd much rather they stuck to something simple like that. This at least won't reject valid email addresses.
|
# ? Feb 12, 2009 14:33 |
|
Zombywuf posted:amivalid@123.23.3 Who cares? There's no guarantee that a well-formed email address is actually a working email address, so what do you actually gain from checking if it's well-formed?
|
# ? Feb 12, 2009 15:40 |
|
tripwire posted:There is no god but PERL and regular expressions are his prophets. Can't figure out whay that popped into my head - I certianly don't like PERL that much.
|
# ? Feb 12, 2009 15:42 |
|
Munkeymon posted:Can't figure out whay that popped into my head - I certianly don't like PERL that much. Perl. Perl. Do you go around saying poo poo like JAVA or RUBY? <>
|
# ? Feb 12, 2009 15:47 |
|
Triple Tech posted:Perl. Perl. Do you go around saying poo poo like JAVA or RUBY? <> Do Java or Ruby stand for something? 'Cuz I'll start doing that if they do.
|
# ? Feb 12, 2009 17:31 |
|
ryanmfw posted:I was thinking more along these lines: Good god, if there is anything that exemplified the title of this thread, this is it.
|
# ? Feb 12, 2009 17:38 |
|
Munkeymon posted:Do Java or Ruby stand for something? 'Cuz I'll start doing that if they do. Perl doesn't either.
|
# ? Feb 12, 2009 17:41 |
|
Plorkyeran posted:Perl doesn't either. Practical extrapolation and report language. Unfortunately, that explanation was created long after Larry had been using the language.
|
# ? Feb 12, 2009 18:13 |
|
royallthefourth posted:Practical extrapolation and report language. If you're going to go for the false etymology, you might as well go for Pathologically Eclectic Rubbish Lister.
|
# ? Feb 12, 2009 18:17 |
|
royallthefourth posted:Practical extrapolation and report language. Considering you can make up backronyms for any word, I guess every proper noun should be written in all caps.
|
# ? Feb 12, 2009 18:26 |
|
6174 posted:If you're going to go for the false etymology, you might as well go for Pathologically Eclectic Rubbish Lister. Yeah, that's really a lot more accurate. Edit: Why the hell did he call it Perl if that didn't stand for something? Or did he just invent a language and then call it something? Munkeymon fucked around with this message at 18:55 on Feb 12, 2009 |
# ? Feb 12, 2009 18:28 |
|
Zombywuf posted:amivalid@123.23.3 I see what you were trying to do, but for what it's worth, that is a valid email address. Direct delivery to IP addresses is acceptable, and that is a valid (although not normalized) IP address. No-one ever does IP address validation correctly.
|
# ? Feb 12, 2009 18:56 |
|
ShoulderDaemon posted:I see what you were trying to do, but for what it's worth, that is a valid email address. Direct delivery to IP addresses is acceptable, and that is a valid (although not normalized) IP address. No-one ever does IP address validation correctly. That was my point (badly expressed). .+@.+ is about the only regex you can use that won't generate false negatives. Another example of this fun is myname@1234567890. Of course root is a valid email address, so even the above creates false negatives, for given values of false. Also can 1.2.3.4 be a valid domain name?
|
# ? Feb 12, 2009 19:17 |
|
Munkeymon posted:Edit: Why the hell did he call it Perl if that didn't stand for something? Or did he just invent a language and then call it something? It was originally Pearl, some biblical reference (pearl of great price?) but he saw some other thing called Pearl so he dropped the a.
|
# ? Feb 12, 2009 19:18 |
|
Plorkyeran posted:Considering you can make up backronyms for any word, I guess every proper noun should be written in all caps. It works for Gary Busey v:)v LISP: Life Incidentially Supplies Powers
|
# ? Feb 12, 2009 19:18 |
|
Zombywuf posted:Also can 1.2.3.4 be a valid domain name? Strictly speaking I think it can be a valid domain name, but none of the toplevels start with numerals, and I don't expect ICANN to ever change that.
|
# ? Feb 12, 2009 19:19 |
|
ShoulderDaemon posted:Strictly speaking I think it can be a valid domain name, but none of the toplevels start with numerals, and I don't expect ICANN to ever change that. rfc1035 posted:Although labels can contain any 8 bit values in octets that make up a 0x07 (visual bell) is a valid domain name component. I wonder if any registrar will accept it...
|
# ? Feb 12, 2009 19:25 |
|
ShoulderDaemon posted:I see what you were trying to do, but for what it's worth, that is a valid email address. Direct delivery to IP addresses is acceptable, and that is a valid (although not normalized) IP address. No-one ever does IP address validation correctly. I don't think amivalid@123.23.3 is direct delivery to an IP address. It's been a while since I read RFC822, but I seem to recall that you need to stick brackets around the IP address. Checking with the local installation of Postfix: code:
|
# ? Feb 12, 2009 19:39 |
|
Munkeymon posted:Yeah, that's really a lot more accurate. Yay for wikipedia! quote:Perl was originally named "Pearl," after the Parable of the Pearl from the Gospel of Matthew. Larry Wall wanted to give the language a short name with positive connotations; he claims that he considered (and rejected) every three- and four-letter word in the dictionary. He also considered naming it after his wife Gloria. Wall discovered the existing PEARL programming language before Perl's official release and changed the spelling of the name.
|
# ? Feb 12, 2009 19:55 |
|
Erasmus Darwin posted:I don't think amivalid@123.23.3 is direct delivery to an IP address. It's been a while since I read RFC822, but I seem to recall that you need to stick brackets around the IP address. Yeah, I think you're right. Silly me.
|
# ? Feb 12, 2009 19:57 |
|
I guess this talk of acronyms just brings us back to the way we program in Perl: Perl is whatever the programmer wants it to be.
|
# ? Feb 12, 2009 20:01 |
|
Erasmus Darwin posted:I don't think amivalid@123.23.3 is direct delivery to an IP address. It's been a while since I read RFC822, but I seem to recall that you need to stick brackets around the IP address. Wow, I've also thought this works. Learn something new everyday. Edit: Having said that, <zombywuf@[2130706433]>: bad address syntax. Anyone fancy reading the rfc for me because I can't be arsed finding out if postfix is getting it wrong. Zombywuf fucked around with this message at 20:21 on Feb 12, 2009 |
# ? Feb 12, 2009 20:16 |
|
The 'not-invented-here' syndrome strikes again!code:
Suppliers send us dates earlier than this all the time, and it just gets stripped from the XML.
|
# ? Feb 12, 2009 20:43 |
|
Trammel posted:The 'not-invented-here' syndrome strikes again! Mmm, I love me some security.
|
# ? Feb 12, 2009 21:49 |
|
quote != edit
|
# ? Feb 12, 2009 21:50 |
|
check out this sweet container (DynamicArray is a homegrown resizable array that's basically std::vector without bounds checking and the added bonus of being completely inscrutable to the visual c++ debugger)code:
raminasi fucked around with this message at 23:07 on Feb 12, 2009 |
# ? Feb 12, 2009 22:23 |
|
I'm curious if there's a difference between DynamicArray::Size() and DynamicArray::GetNumb().
|
# ? Feb 12, 2009 22:29 |
|
Plorkyeran posted:Indeed, Wall claims that the name was intended to inspire many different expansions.[14] I swear that guy would be most happy living in the programmer's district of Toonland or whatever it was from Roger Rabbit. quote:What's your language today, Larry?
|
# ? Feb 12, 2009 22:57 |
|
rjmccall posted:There isn't, actually - I just changed the method name to make it a little more clear to people reading but forgot that one. Whoops!
|
# ? Feb 12, 2009 23:08 |
|
GrumpyDoctor posted:check out this sweet container (DynamicArray is a homegrown resizable array that's basically std::vector without bounds checking and the added bonus of being completely inscrutable to the visual c++ debugger) home-grown wheel reinvention, difficult to debug, the lack of reference parameters/returns and an always O(n^2) bubble sort. Beautiful
|
# ? Feb 13, 2009 00:47 |
|
Avenging Dentist posted:Or that they expected you to write a simple parser instead of using a regex. Also, I think that regex should be treated like a magiceye picture and perhaps it's all a cruel joke and you get goatse'd.
|
# ? Feb 13, 2009 07:09 |
|
|
# ? Apr 29, 2024 08:31 |
|
RFC 822 predates the web by a decade.. and web services by two.
|
# ? Feb 13, 2009 08:11 |