|
From: | Neil Jerram |
Subject: | Re: guile-lib things |
Date: | Thu, 01 Jul 2004 22:42:53 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux 2.4.4-4GB i686; en-US; 0.8.1) Gecko/20010515 |
Hi Andy,FWIW, I agree with the apparent consensus on all the points that have been made following your email, i.e.:
- avoid hierarchy for package names - but hierarchy within a package can be useful- consider standardizing a method for declaring keywords, then a search on those would provide the benefits of a hierarchical package namespace, but without the problems.
One other thought that I don't believe has been covered... Andy Wingo wrote:
Hey folks, I've been integrating some code from other people into guile-lib. It's tricky. The conflict is the coherence of guile-lib versus the coherence of the upstream code itself. If the package is being currently maintained, such as SSAX, you can't really change much, because otherwise maintainance will be a nightmare, and the authors might call your version heretical or something. However, you can't *not* modify at all, because you at least have to add module headers and exports.
What is wrong with just this? ;;; GUILE-LIB copyright block (define-module (ssax) #:export (...)) (load "upstream/ssax.scm")(I daresay there is some problem with this, but I suspect we need to get into details to pin it down and find a solution.)
Regards, Neil
[Prev in Thread] | Current Thread | [Next in Thread] |