----- Original Message ---- From: chromatic <[EMAIL PROTECTED]> > On Monday 17 July 2006 05:19, demerphq wrote: > > > The fact that it does the same thing every time for a given set of > > input doesnt mean that it does the RIGHT thing. And i dont see how its > > possible to automatically do the right thing every time. Therefore if > > you need a custom wrapper you need to teach it to do the right thing. > > If you write buggy code you'll sometimes get the wrong answers. That's sort > of a tautology.
It's a lot easier to write buggy code in assembler than in Perl. A good interface design makes it easier to write good code and the Perl language is a better interface to the CPU than assembler if you're willing to accept the trade-offs it presents. If TAP::Harness and friends are going to be assembled, I think focusing on issues like this is a good thing. For example, what could be done in TAP::Harness to improve the reporting on line numbers? That alone would be a nice benefit for folks. Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
