On Wed, 29 Aug 2018 14:17:08 +0200 felix.winkelm...@bevuta.com wrote:
> > [...]
> > I can't say that I like this design decision, but I guess I'll have to
> > live with it. If this is unsupported, it also feels strange that
> > the .egg format allows specification of multiple import libraries per
>
> I can't say that I like this design decision, but I guess I'll have to
> live with it. If this is unsupported, it also feels strange that
> the .egg format allows specification of multiple import libraries per
> extension at all – the provider side of the picture, when you write a
> library
On Tue, 28 Aug 2018 20:40:33 +0200 felix.winkelm...@bevuta.com wrote:
> [...]
> I'll try to address some of your questions.
> [...]
Hello,
thanks for taking the time to reply :-)
> [...]
> > - Some eggs install one extension library containing several modules. The
> > new
> > CHICKEN module
Hi, Thomas!
I'll try to address some of your questions.
> - Some eggs install one extension library containing several modules. The new
> CHICKEN module system always tries to load a library named the same as the
> module upon import. Is it no longer possible to separate library loading and
>
Hello,
playing with the new CHICKEN 5 module system and egg format raised a couple of
questions in my head – perhaps someone on this list can provide a few answers
:-)
- Some eggs install one extension library containing several modules. The new
CHICKEN module system always tries to load a
