Re: [Chicken-hackers] [PATCH] Add initial version of (chicken base)

[felix . winkelmann]

>
> Agreed, let's drop those from (chicken base).  This includes the
> "enable-warnings" procedure, because it makes no sense to have a way
> of programmatically enabling/disabling warnings that only the core
> tools should be emitting anyway.

I would leave "warning" and "enable-warnings", as we expose "error"
too. It has uses - "notice" is different, and can be replaced by a (trivially)
implemented user-made logging facility. This may sound a bit like bikeshedding,
but we will break a bit of code otherwise.

> > The `require-extension` macro can go in a srfi-55 egg.
>
> I think it makes more sense to keep it in core, for compatibility with
> the srfi.  Maybe we can clarify in the documentation that it's just an
> alias for (import)?  I think (use) is a bit more questionable, now that
> it's also just an alias for (import).

Agreed.

>
> require-library is so weird and does so much (at least, it looks like it
> does from the docs), I don't know what to do with it.  Maybe we can indeed
> just remove it?

It should be possible to link with units, but I guess that can be done via 
"declare".
If that is still possible then "require-library" may indeed go.


felix