From: Andy Wingo <wingo@pobox.com>
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: guile-lib things
Date: Thu, 08 Jul 2004 20:09:44 +0100 [thread overview]
Message-ID: <1089313784.19379.68.camel@localhost> (raw)
In-Reply-To: <40E4855D.2050200@ossau.uklinux.net>
Hi Neil,
On Thu, 2004-07-01 at 22:42 +0100, Neil Jerram wrote:
> One other thought that I don't believe has been covered...
>
> What is wrong with just this?
>
> ;;; GUILE-LIB copyright block
>
> (define-module (ssax)
> #:export (...))
>
> (load "upstream/ssax.scm")
I like it. I don't know why this didn't occur to me.
This also allows documentation, in the form of commentaries, and as the
'documentation object property. A support macro would be nice, something
like (define-docs var docs) or so.
The only problem I see with this is if there are guile-specific
optimizations relevant to a package. Then you have to maintain a set of
private diffs. But that's not so much maintainance.
(BTW, I think ssax is part of a family of sxml processing tools produced
by oleg&co, so I call it (sxml ssax). Seems reasonable. But no
non-ssax.sf.net projects should go there.)
Thanks for the input, yo.
--
Andy Wingo <wingo@pobox.com>
http://ambient.2y.net/wingo/
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2004-07-08 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 18:03 guile-lib things Andy Wingo
2004-06-25 11:48 ` Andy Wingo
2004-06-25 18:31 ` Rob Browning
2004-06-27 21:43 ` Linas Vepstas
2004-06-29 17:43 ` Andy Wingo
2004-06-30 22:20 ` Rob Browning
2004-07-08 19:01 ` Andy Wingo
2004-07-03 16:48 ` Thien-Thi Nguyen
2004-07-10 4:44 ` Linas Vepstas
2004-06-27 1:22 ` ASDF for guile (Was Re: guile-lib things) Chris Hall
2004-06-28 13:33 ` Matthew Trout
2004-06-28 13:48 ` Andy Wingo
2004-07-01 21:42 ` guile-lib things Neil Jerram
2004-07-08 19:09 ` Andy Wingo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1089313784.19379.68.camel@localhost \
--to=wingo@pobox.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).