I've got to agree with Rob on this one.  I appreciate the concern for  
other group members.  It keeps all of us honest, and polite.  I can  
be a bit abrasive at times, especially via email. It's usually not  
intended.  (Unless I'm responding to someone who a) hasn't read the  
archives from even the previous _day_, and b) clearly didn't bother  
to use Google before asking an oft-repeated question.)

Part of the trouble with an email validation regex is a) it's a  
common request on the internet, b) every body has their own version,  
and c) hardly anyone gets it right.  It is IMHO, in most cases, the  
wrong way to solve a particular problem.

The principles at work here are:
1. Code should attempt to be timeless.  A programmer should write  
code believing it will be in use in a couple hundred years (without  
needing to be fixed).
2. When validating, accepting "bad" data is usually preferable to  
rejecting "good" data.

More comments inline, below.

On Jul 6, 2007, at 1:22 AM, RobG wrote:

> Knowing whether ... is the author or the code has been published
> helps to determine whether it was intended it to be used as a general
> email checking script and who to contact for permission to use it.  If
> anyone posts code that they didn't write, they should *always* state
> where it came from.

Yes, but I think there's an implicit understanding (correct or not)  
that small posted snippets are for general use.

> The fact that something someone posted is criticised should not be
> seen as negative, neither Tom nor I said anything harsh.    The main
> benefit of a public group is that anyone can review and comment on
> anything that is posted here - hopefully constructive criticism
> outweighs negative.

I've posted code/ideas several times, only to have the idea  
"improved" (read: corrected) by some of the exceptional programmers  
here.  One of the reasons I like participating is the number of  
exceptionally smart people that regularly contribute.  One of the  
ways I learn is to identify the flaws in my code/methods.  People  
here help with that (politely), and I appreciate it.

> Perhaps I should include plenty of smilies :-) when providing advice
> next time. ;-)

<chuckle>


TAG

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Spinoffs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-spinoffs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to