Re: [dev] [sbase] [PATCH] uuencode base64 encoding/decoding and stdout output for uudecode

From: Dimitris Papastamos <sin_AT_2f30.org>
Date: Fri, 13 Feb 2015 09:56:59 +0000

On Fri, Feb 13, 2015 at 10:41:08AM +0100, FRIGN wrote:
> This is not the case anymore in big commercial programs, but this is
> far from the desired state. A modular approach, where you can assess
> that each part works as expected, can be way superior.
> If you make a change to a tool and can't be sure that it modifies
> edge-cases, there's something wrong with the program.

It is also not the case if you want to test a very large number of
well-defined set of semantics. musl libc has a test[0] repo for this
purpose. This is however, outside the scope of sbase due to the
much lower complexity that we have to deal with. People should not
solely rely on the results of some automated testing however, but it
can help at times.

[0] http://git.musl-libc.org/cgit/libc-testsuite/
Received on Fri Feb 13 2015 - 10:56:59 CET

This archive was generated by hypermail 2.3.0 : Fri Feb 13 2015 - 11:00:18 CET