From: Daniel Skarda <0rfelyus@ucw.cz>
Cc: Rob Browning <rlb@defaultvalue.org>,
Neil Jerram <neil@ossau.uklinux.net>,
guile-devel@gnu.org
Subject: Re: Adding stuff to the core distro (was Re: Infix syntax)
Date: 20 Oct 2002 22:25:45 +0200 [thread overview]
Message-ID: <m0hefgdfhy.fsf@hobitin.ucw.cz> (raw)
In-Reply-To: <02101802244004.07034@locke.free-expression.org>
Lynn Winebarger <owinebar@free-expression.org> writes:
> Why can't I define a bunch of little modules (possible with dependencies)
> and then load those into srfi-1 which then exports all those names as one big group?
> [ Or just load the subset I actually want/need ]
AFAIK it is possible (see for example srfi-2 and re-export) but
unfortunately srfi-1 is not implemented this way :-(
Short list of other module faux pas:
- two list libraries - srfi-1 and ice-9/common-list. Both of them
implement `every' etc.
I guess module names like (list foo) would be very boring...
- structs (guile-core), make-record (boot-9), define-struct (match,
psyntax), define-record-type (srfi-9), define-class (goops).
> The goal is not a small set of dependencies (per se). It's just cleaner to keep
> code from having more knowledge about other code than it should. SE101. I
> think it's a little easier to enforce this minimalism of code knowledge if you actually
> keep code in separate directories. If anything, I'd probably advocate separating
> what's in the libguile directory now into smaller, mostly independent directories,
> where a developer could be reasonably certain that to understand a piece of
> code in a file they probably would only need to look at other files in that subdirectory,
> or possibly in some header files (or possibly other subdirectories closer to the real
> core code, i.e. eval.c).
I understand. I do not oppose to separate code into directories. I just do
not understand why Guile _development_ is so separated - guile-core here,
guile-debugger over there etc.
I do not propose to put everything into libguile or boot-9. I propose more
centralised development - distribute with guile everything somebody may find
useful (so he can directly start using guile for some specific task - no
need to search inet etc), develop everything together (lower maintenance
cost), make Guile more attractive.
SE (Scheme Elephant :-),
0.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-10-20 20:25 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
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 [this message]
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=m0hefgdfhy.fsf@hobitin.ucw.cz \
--to=0rfelyus@ucw.cz \
--cc=guile-devel@gnu.org \
--cc=neil@ossau.uklinux.net \
--cc=rlb@defaultvalue.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).