From: Andreas Rottmann <a.rottmann@gmx.at>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "Andy Wingo" <wingo@pobox.com>, "Ludovic Courtès" <ludo@gnu.org>,
guile-devel@gnu.org
Subject: Re: Fmt Module
Date: Mon, 28 Mar 2011 01:24:16 +0200 [thread overview]
Message-ID: <87k4fkjgf3.fsf@gmx.at> (raw)
In-Reply-To: <AANLkTi=Gj-bRZSrue47-T7681SVBHiaAgwUa0J9-8nW5@mail.gmail.com> (Noah Lavine's message of "Sun, 27 Mar 2011 11:38:09 -0400")
Noah Lavine <noah.b.lavine@gmail.com> writes:
> Hello,
>
>>> I think it would make sense to include ‘fmt’ in core Guile only if the
>>> API is reasonably stable and there are infrequent upstream releases, so
>>> we don’t quickly end up shipping an old incompatible version.
>>
>> Agreed, and I don't know if this is the case or not.
>>
>> I would add on another criteria, that we should avoid adding modules to
>> Guile unless they are to be used in Guile itself. For everything else,
>> there is our CPAN that we need to make -- it will provide more freedom
>> both for module authors/packagers and for users.
>
> This makes sense, but I think there is an important distinction to
> make that we do not currently make. We should have a clear idea of
> what modules are used by Guile, so we can get a "minimal" Guile when
> we want it, for instance for embedding into other applications.
>
+1! Racket has acquired a problem with that over the years, and there
are now efforts to rectify it [0].
[0] http://www.mail-archive.com/dev@racket-lang.org/msg02376.html
> However, it would be great if the standard install of Guile included
> lots of modules, such as htmlprag, because it is nice to have the
> batteries included when you are programming.
>
My opinion on that is that if it's really easy to install additional
libraries (which is not yet the case, unfortunatly!), there would be no
need to bundle additional stuff not needed by the core into Guile
releases.
Regards, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
prev parent reply other threads:[~2011-03-27 23:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-12 21:14 Fmt Module Noah Lavine
2011-03-13 21:37 ` Andreas Rottmann
2011-03-14 3:54 ` Noah Lavine
2011-03-14 17:16 ` Ludovic Courtès
2011-03-14 17:35 ` Klaus Schilling
2011-03-27 11:07 ` Andy Wingo
2011-03-24 0:45 ` Andreas Rottmann
2011-03-24 21:14 ` Ludovic Courtès
2011-03-26 14:03 ` Andreas Rottmann
2011-03-27 14:01 ` Ludovic Courtès
2011-03-27 11:10 ` Andy Wingo
2011-03-27 15:38 ` Noah Lavine
2011-03-27 23:24 ` Andreas Rottmann [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=87k4fkjgf3.fsf@gmx.at \
--to=a.rottmann@gmx.at \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=noah.b.lavine@gmail.com \
--cc=wingo@pobox.com \
/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).