>>>>> "Silent" == Silent Zed <[EMAIL PROTECTED]> writes:
Silent> I'd like to know the thought's of other people are on this Silent> though, was I wrong to post a quick and dirty solution to a Silent> problem? The problem with that kind of a response is that it's likely to get picked up out of context, and used for *all* email address parsing. That's the behavior I hoped to stop. And yes, I overreacted, but how else do you kill the bad meme! In other words, don't call that a regex that "can match email addresses". Label it a regex "that matches some common email addresses". It's a bit like including (making it relevant here again) the cargo-culted %ENV-parser to the params into a flat hash, as long as you don't have select-multiples or uploaded files. I will flag that *every* time as bad practice, simply because it's neither necessary nor sufficient. I'm fighting the bad memes, and the people who repeat them. If there's a few bodies along the way, that's necessary, IMHO. If the only effect is to scare someone into never answering again, then at least they won't be publishing that *bad* answer again. On the flip side, there are very few things that I get this riled up about. :-) Bad memes, security holes, hiding code, and one other thing that escapes me now. The rest, I live and let live. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <[EMAIL PROTECTED]> <URL:http://www.stonehenge.com/merlyn/> Perl/Unix/security consulting, Technical writing, Comedy, etc. etc. See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training! -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
