No GnuPG library for now

Taral taral at
Fri Oct 20 00:10:10 CEST 2000

Quoting Frank Tobin <ftobin at>:

> > > * List all functionality in the system
> > > * Partition the system into modules
> > > * Define the exposed part of each module
> > > * Define the inter-module dependencies
> > > * Create the API for the modules
> > 
> > That is a lot of work and I prefer to invest the time in auditing and
> > making the code cleaner.
> This is exactly the approach that software engineering courses and
> books
> teach against (unless you are doing XP, of course, which GnuPG doesn't
> seem to be doing).

Well, I _am_ an XP advocate to a certain extent. It always made sense to me. 
What I listed is basically what every large software project I work on 
eventually has had to do to avoid becoming spaghetti (or worse).

Taral <taral at>
This mail sent through the UT Austin Webmail service,

More information about the Gnupg-devel mailing list