From: Richard Todd <richardt@vzavenue.net>
Cc: guile-user@gnu.org
Subject: Re: First look at Guile Std Library available
Date: Sat, 3 Jan 2004 16:52:26 -0600 [thread overview]
Message-ID: <20040103225226.GC518@Richard-Todds-Computer.local> (raw)
In-Reply-To: <E1AconE-000479-00@surf.glug.org>
[-- Attachment #1.1: Type: text/plain, Size: 1771 bytes --]
On Sat, Jan 03, 2004 at 05:38:28PM +0100, Thien-Thi Nguyen wrote:
> From: Richard Todd <richardt@vzavenue.net>
> Date: Thu, 1 Jan 2004 23:21:28 -0600
>
> Every time someone does this and contributes it to the
> library, the entire guile community gets more efficient.
>
> this is debatable. a numerical recipe derived from slib (for example)
> has potential to suffer bit-rot when slib is enhanced. i see that slib
> now has a module system of sorts; maybe you could codify the derivation
> methodology (steps to translate code from "slib module" format to "guile
> module" format) so that it could be applied to each slib release, to
> reduce your project's maintenance burden.
Yes, there will be maintenance to do when significant changes to the
source material appear. I don't have a really good answer for that
problem, since anything but copying and (slightly) modifying their
sources conflics with the other goals I have for the project.
What I have done, is start a mapping between the project modules and
their SLIB sources. I'm not sure, but if I re-sync with SLIB once a
year or so, that doesn't seem like too much of a maintenance headache.
I may feel differently the first time I actually have to *do* it!
For the stuff already written for guile that gets pulled in, I hope
the maintainers will either maintain their modules as part of the
standard lib, or actively help push their changes into the library at
their major updates.
This topic is definitely still up for debate.. I have pulled in some
SLIB sources as examples of what it would look like, but I have no
problem completely changing direction on that issue if guile users
think it would be best.
Richard Todd
richardt at vzavenue dot net
[-- Attachment #1.2: Type: application/pgp-signature, Size: 186 bytes --]
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-01-03 22:52 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 5:21 First look at Guile Std Library available Richard Todd
2004-01-02 9:29 ` Dale Mellor
2004-01-03 1:03 ` Richard Todd
2004-01-03 2:25 ` Andreas Rottmann
2004-01-03 15:00 ` Dale Mellor
2004-01-03 14:36 ` Dale Mellor
2004-01-03 22:42 ` Richard Todd
2004-01-03 16:38 ` Thien-Thi Nguyen
2004-01-03 16:48 ` Nic Ferrier
2004-01-03 22:18 ` Richard Todd
2004-01-04 1:49 ` Thien-Thi Nguyen
2004-01-04 3:50 ` Richard Todd
2004-01-04 12:59 ` Thien-Thi Nguyen
[not found] ` <16376.5782.10995.206284@l.a>
2004-01-04 14:17 ` Dale Mellor
2004-01-04 21:51 ` Richard Todd
2004-01-05 0:30 ` Andreas Rottmann
2004-01-05 5:00 ` Richard Todd
2004-01-05 16:03 ` Robert Uhl
2004-01-05 20:01 ` Richard Todd
2004-01-06 1:36 ` Robert Uhl
2004-01-06 18:41 ` number->string radix patch (Was Re: First look at Guile Std Library available) Richard Todd
2004-01-07 4:04 ` Robert Uhl
2004-01-07 5:26 ` Richard Todd
2004-01-07 20:54 ` Robert Uhl
2004-01-08 7:11 ` I get unknown immediate error in guile 1.7 Roland Orre
2004-01-08 17:14 ` Roland Orre
2004-01-10 20:17 ` Kevin Ryde
2004-05-10 20:34 ` number->string radix patch Marius Vollmer
2004-05-11 3:16 ` Richard Todd
2004-05-11 3:51 ` Keith Wright
2004-05-27 21:56 ` Kevin Ryde
2004-06-10 16:35 ` Marius Vollmer
2004-06-10 16:34 ` Marius Vollmer
2004-05-11 5:23 ` Richard Todd
2004-05-27 21:54 ` Kevin Ryde
2004-06-10 16:47 ` Marius Vollmer
2004-06-11 1:40 ` Kevin Ryde
2004-01-05 10:08 ` First look at Guile Std Library available Dale Mellor
2004-01-05 3:39 ` Paul Jarc
2004-01-05 4:28 ` Richard Todd
2004-01-05 5:19 ` Paul Jarc
2004-01-06 22:25 ` Ludovic Courtès
2004-01-06 23:53 ` Richard Todd
2004-01-16 20:17 ` Andy Wingo
2004-01-05 14:00 ` Thien-Thi Nguyen
2004-01-05 20:32 ` Richard Todd
2004-01-05 20:59 ` Dale P. Smith
2004-01-06 16:54 ` Thien-Thi Nguyen
2004-01-06 20:32 ` Richard Todd
2004-01-03 18:19 ` Clinton Ebadi
2004-01-03 20:12 ` Thien-Thi Nguyen
2004-01-04 2:02 ` Richard Todd
2004-01-06 20:42 ` Richard Todd
2004-01-06 21:20 ` Paul Jarc
2004-01-03 22:52 ` Richard Todd [this message]
2004-01-04 1:53 ` Thien-Thi Nguyen
2004-01-04 20:34 ` Arno Peters
2004-01-05 20:12 ` Richard Todd
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=20040103225226.GC518@Richard-Todds-Computer.local \
--to=richardt@vzavenue.net \
--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).