unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Daniel Skarda <0rfelyus@ucw.cz>, guile-devel@gnu.org
Subject: Re: Adding stuff to the core distro (was Re: Infix syntax)
Date: Tue, 08 Oct 2002 22:30:52 -0500	[thread overview]
Message-ID: <87u1jwi903.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <m37kgsbnvf.fsf@laruns.ossau.uklinux.net> (Neil Jerram's message of "08 Oct 2002 22:51:32 +0100")

Neil Jerram <neil@ossau.uklinux.net> writes:

> On the other hand...  Rob has raised the question of whether we should
> be adding things to the core distro that don't strictly need to be
> there, so perhaps we should stop for a moment to consider our
> principles on this point.

I not all that concerned with things that require an explicit
activation.  I'm more concerned with any additions to what's visible
in the core of guile (guile) and (guile-user) at startup, and more
particularly, how much happens in ice-9/boot-9.scm, though to some
extent that's an efficiency issue as much as a semantic issue.

I do think it would be nice if eventually guile were separable to the
extent that it was easy to install a "guile-base" that was perhaps
much smaller than "guile-base + guile-foo + guile-bar", but I'm not
saying I know how things should be broken up in to guile-base,
guile-foo, and guile-bar...

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  parent reply	other threads:[~2002-10-09  3:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 11:26 Infix syntax Daniel Skarda
2002-10-05  8:55 ` Neil Jerram
2002-10-06  8:05   ` Daniel Skarda
2002-10-08 21:51     ` Adding stuff to the core distro (was Re: Infix syntax) Neil Jerram
2002-10-08 22:40       ` Han-Wen Nienhuys
2002-10-09  3:30       ` Rob Browning [this message]
2002-10-09 18:15         ` Neil Jerram
2002-10-09 20:17           ` Rob Browning
2002-10-10 12:20             ` Daniel Skarda
2002-10-10 12:29       ` Daniel Skarda
2002-10-13 14:28         ` Neil Jerram
2002-10-16 21:35           ` Daniel Skarda
2002-10-19  4:50             ` tomas
2002-10-20 19:15               ` Daniel Skarda
2002-10-21  9:36                 ` tomas
2002-10-21 18:21                 ` Neil Jerram
2002-10-19 22:17             ` Christopher Cramer
2002-10-20 19:05               ` Daniel Skarda
2002-10-10 16:06       ` Daniel Skarda
2002-10-10 17:12         ` Rob Browning
2002-10-10 18:46           ` Clinton Ebadi
2002-10-10 22:24           ` Lynn Winebarger
2002-10-13 15:09           ` Proposal for scope of core distro Neil Jerram
2002-10-17  0:10           ` Adding stuff to the core distro (was Re: Infix syntax) Daniel Skarda
2002-10-18  7:24             ` Lynn Winebarger
2002-10-20 20:25               ` Daniel Skarda
2002-10-10 18:08         ` Bill Gribble
2002-10-17  2:42           ` Daniel Skarda
2002-10-13 14:27         ` Neil Jerram
2002-10-17  1:25           ` Daniel Skarda
2002-10-19 10:56             ` Neil Jerram

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=87u1jwi903.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=0rfelyus@ucw.cz \
    --cc=guile-devel@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).