[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-hackers] too many core modules?
From: |
felix winkelmann |
Subject: |
Re: [Chicken-hackers] too many core modules? |
Date: |
Tue, 1 Sep 2009 13:20:49 +0200 |
2009/9/1 Peter Bex <address@hidden>:
>
>> 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.
Loaded by default are library, eval, data-structures, extras, ports
and srfi-69. At some stage
we should remove all but library and eval from this list. A
"big-chicken" unit would
combine data-structures, extras, files, ports and utils.
cheers,
felix
- [Chicken-hackers] too many core modules?, felix winkelmann, 2009/09/01
- Re: [Chicken-hackers] too many core modules?, Peter Bex, 2009/09/01
- Re: [Chicken-hackers] too many core modules?,
felix winkelmann <=
- Re: [Chicken-hackers] too many core modules?, Alex Shinn, 2009/09/01
- Re: [Chicken-hackers] too many core modules?, John Cowan, 2009/09/01
- Re: [Chicken-hackers] too many core modules?, John Cowan, 2009/09/01
- Re: [Chicken-hackers] too many core modules?, felix winkelmann, 2009/09/02
- Re: [Chicken-hackers] too many core modules?, John Cowan, 2009/09/02