[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] too many core modules?
From: |
Peter Bex |
Subject: |
Re: [Chicken-hackers] too many core modules? |
Date: |
Tue, 1 Sep 2009 10:10:36 +0200 |
User-agent: |
Mutt/1.4.2.3i |
On Tue, Sep 01, 2009 at 09:57:47AM +0200, felix winkelmann wrote:
> Hello!
>
> It's probably just me, but if I have to write "(use ports files
> data-structures utils extras)" one more
> time, I'll go crazy.
>
> I think the splitting up of the extras unit was done haphazardly. It
> doesn't really give any
> benefit to split up the library fo chicken extensions, since loading
> one or two eggs will drag in
> most of them anyway. I think it's ok to keep the SRFIs separate.
Agreed.
> Therefore I'd like to introduce a new library unit (say
> "chicken-stuff" [*]) that for the time
> being just loads the other units and provides the necessary imports.
[...]
>
> [*] a lame name - any suggestions are welcome
I know! Let's call it "pretty-big"!
</tongue-in-cheek>
> Is it ok to make this change, or does somebody see a problem with this?
Explicitly listing all units that are already loaded in core anyway is
a bit silly, indeed. If it actually causes some code to be loaded, it
makes sense to have to import it.
Cheers,
PEter
--
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
is especially attractive, not only because it can be economically
and scientifically rewarding, but also because it can be an aesthetic
experience much like composing poetry or music."
-- Donald Knuth
pgplrD3guaSK4.pgp
Description: PGP signature