[Top][All Lists]

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

[Chicken-hackers] [PATCH] Use the same "default imports" at toplevel out

From: Peter Bex
Subject: [Chicken-hackers] [PATCH] Use the same "default imports" at toplevel outside modules in compiled and interpreted code
Date: Fri, 24 Nov 2017 23:05:19 +0100
User-agent: NeoMutt/20170113 (1.7.2)

Hi all,

I noticed that in csi, we're importing "scheme" and "chicken" by default at
the toplevel, whereas in compiled code we're importing "scheme", "chicken"
and "chicken.base".

The attached patch makes this consistent again by moving it to one definition
in the chicken.internal module.  It also removes "chicken" from the list and
(somewhat arbitrarily) adds chicken.syntax as well so {er,ir}-macro-transformer
are available by default, just like syntax-rules is.

And lots and lots of changes to tests which relied on various stuff from the
"chicken" module being available by default.


Attachment: 0001-Make-default-imports-consistent-between-interpreter-.patch
Description: Text Data

Attachment: signature.asc
Description: PGP signature

reply via email to

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