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: Tue, 12 Sep 2017 11:59:58 +0200
User-agent: NeoMutt/20170113 (1.7.2)

On Tue, Sep 12, 2017 at 10:51:56AM +0200, address@hidden wrote:
> > - notice (we already had "warning" and "error", however, notice seems
> >           to be used mostly in the compiler)
> 
> Does this need to be exposed? I'm not sure how useful this is for user
> code.

Currently ##sys#notice is used by ##sys#import when re-importing
identifiers.  Maybe it could be useful for user macros as well, if one
wants to allow the user to enable / disable these notices.

> > - use
> > - require-library
> > - require-extension
> >
> > I'm not 100% sure about require-library, require-extension and use,
> > especially given that import is in (chicken module).
> 
> Hm... I thought we try to get rid of all these alternative loading forms?

I think that's still a TODO (we can of course do that afterwards).

> > I'm less certain what we should add to the non-macro toplevel default
> > Perhaps (chicken type), (chicken fixnum), (chicken flonum) and
> > (chicken foreign) [the latter for compiled code], but we could also
> > keep it otherwise empty, or even add everything from library.scm, much
> > like we do today in CHICKEN 4.  This would make it easier for scripts,
> > but perhaps a bit more confusing for beginners ("what do you mean,
> > sometimes I have to import and sometimes it's already there?!!")
> 
> Does this apply to interpreted or compiled code? My assumption was
> that only the base stuff is initially visible.

I don't know really; I got compilation errors but those may be due to
macros that failed (which is interpreted code).

Cheers,
Peter

Attachment: signature.asc
Description: PGP signature


reply via email to

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