Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

runrig (3385)

runrig
  dougwNO@SPAMcpan.org

Just another perl hacker somewhere near Disneyland

I have this homenode [perlmonks.org] of little consequence on Perl Monks [perlmonks.org] that you probably have no interest in whatsoever.

I also have some modules [cpan.org] on CPAN [cpan.org] some of which are marginally [cpan.org] more [cpan.org] useful [cpan.org] than others.

Journal of runrig (3385)

Thursday December 01, 2005
08:04 PM

Backward compatibility

[ #27822 ]

You can try to be backward compatible, but sometimes it's just better not to be. What if there was an XML parser that was missing some check for an invalid format, so you add the check, and someone who has been running the parser on the same (unknowingly incorrectly formatted) file day after day suddenly has their program blow up when they update the parser?

Of course, you should test before you update critical stuff...so caveat emptor, as always. And I'm not really talking about XML anyway, just my own glorified version of pack/unpack, Parse::FixedLength, where I noticed some errors that weren't being caught, and then some tests that broke when I started catching those errors. Although some may wonder why you would use such a module (see the thread that started it all), there are people that do use it (including me :), and I've found that changes do affect people. I'm just glad I wasn't sued :-)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.