chicken-hackers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH] Add initial version of (chicken base)
Date: Sat, 16 Sep 2017 20:14:00 +0200
User-agent: NeoMutt/20170113 (1.7.2)

On Sat, Sep 16, 2017 at 08:00:28PM +0200, address@hidden wrote:
> >
> > 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.

I tend to think of "error" as different.  For one, it's a SRFI, and for
another, there's lots of user code using it.

> 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.

Note that the second patch I supplied doesn't remove "notice" or "warning",
it merely keeps them at the toplevel in library.scm, so we can later decide
what to do with it.

> > 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.

Yeah, I think that's still possible.

Cheers,
Peter

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]