How not to check the validity of an email address

Re:How not to check the validity of an email address by cperciva on Wednesday September 04, 2013 @03:04PM (#6329684)

I think you're misunderstanding the term. Legacy code -- like legacy lots of other things -- is the intersection of "bad" and "it's too late to fix now".

Code which can be fixed easily isn't "legacy". Code where a replacement would need to be bug-for-bug compatible in order to avoid breaking things is "legacy".

[ Parent | on HN ]

Re:How not to check the validity of an email address by ante_annum on Thursday September 05, 2013 @12:26PM (#6335076)

My favorite definition of legacy code is bad code for which no tests exist. It's terrible because people have no idea what to do with it and no idea what they're breaking when they change it.

You could be writing legacy code today.

[ Parent | on HN ]

Re:How not to check the validity of an email address by sopooneo on Thursday September 05, 2013 @09:59AM (#6334198)

I've heard of that scenario, but I'm curious about what the best way to produce a bug-for-bug replacement would be. Should you do it right, and then put a layer in front of it that switches/transforms the output to match the old errors?

[ Parent | on HN ]