No GnuPG library for now

[Enzo Michelangeli]

For a reply from the real world, see:

http://www.fourmilab.ch/autofile/www/chapter2_108.html

Enzo

----- Original Message ----- 
From: "Frank Tobin" <ftobin@uiuc.edu>
To: <gnupg-devel@gnupg.org>
Sent: Friday, October 20, 2000 3:17 AM
Subject: Re: No GnuPG library for now


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Werner Koch, at 17:23 +0200 on Thu, 19 Oct 2000, wrote:
> 
> > I can't agree.  At least from my experience with Evolution, the
> > problem is that there are so many libaraiers and interfaces and
> > everything depends on each other - which is good of course.  As
> > long as those interfaces are not yet frozen and stable it is
> > complicated to build the thing.  Frankly, it is not complicated, but
> > you need to do many, many cvs updates, and build in the right order.
> 
> Interfaces are always frozen if you design well at the beginning.
> 
> > > * 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).
> 
> - -- 
> Frank Tobin http://www.uiuc.edu/~ftobin/
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (FreeBSD)
> Comment: pgpenvelope 2.9.0 - http://pgpenvelope.sourceforge.net/
> 
> iEYEARECAAYFAjnvSM0ACgkQVv/RCiYMT6MTQACdH4LTLo0fapimV+JrYbd4JGtx
> XqEAnRtuqAg4MN5FCEq5g67Mr2kM+Pfz
> =TgDu
> -----END PGP SIGNATURE-----