unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: Guile Development <guile-devel@gnu.org>
Subject: Re: Plan for guile-debugging integration
Date: Wed, 19 Jul 2006 09:47:14 +0200	[thread overview]
Message-ID: <877j2a3ukd.fsf@laas.fr> (raw)
In-Reply-To: <87fygyu83o.fsf@ossau.uklinux.net> (Neil Jerram's message of "Tue, 18 Jul 2006 18:38:03 +0100")

Hi,

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

> I think we should we wait until there's a big enough mass of Guile
> stuff out there that the current organization becomes a problem.  When
> we have a real problem to solve, we'll probably have a better idea
> about the solution.

Well, there is no real problem to solve, just the fact that `ice-9' is a
silly name.  :-)

Plus the fact that it contains a zillion of unrelated modules, all at
the same level.  I'd be more in favor of a three-level hierarchy which
would typically be something like `(PACKAGE SUB-SYSTEM FEATURE)'.  So,
for Guile, everything would be under `system':

  system
    debugging
    reader     <-- I use that for `guile-reader'
    il
    vm

Removing `ice-9' may not be feasible (for compatibility reasons).
However, using a cleaner name space for *new* modules (like yours) looks
appealing.

Unless people really aren't bothered at all.  ;-)

Thanks,
Ludovic.


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


      parent reply	other threads:[~2006-07-19  7:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-16 17:01 Plan for guile-debugging integration Neil Jerram
2006-06-19  7:41 ` Ludovic Courtès
2006-06-23 13:25   ` Neil Jerram
2006-06-27 11:24     ` Ludovic Courtès
2006-07-18 17:38       ` Neil Jerram
2006-07-19  0:14         ` Kevin Ryde
2006-07-19  7:47         ` Ludovic Courtès [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=877j2a3ukd.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --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).