[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-hackers] [PATCH] Move last few macros out of chicken [was: Re:
From: |
Peter Bex |
Subject: |
[Chicken-hackers] [PATCH] Move last few macros out of chicken [was: Re: What to do with remaining macros?] |
Date: |
Sun, 25 Feb 2018 11:58:17 +0100 |
User-agent: |
NeoMutt/20170113 (1.7.2) |
On Sat, Feb 24, 2018 at 05:25:00PM +0100, Peter Bex wrote:
> Hi all,
>
> I just tagged and built a 5.0.0pre5 snapshot with the intention of then
> dropping the "chicken" module, only to find out that I had forgotten we
> still have several macros being exported by (only) the chicken module.
>
> What should we do with these? My suggestions in square brackets
>
> - time [chicken.time]
> - assert [chicken.base]
> - ensure [chicken.type]
> - eval-when [chicken.base, or just get rid of it?]
> - select [chicken.base, or just get rid of it?]
> - define-for-syntax [chicken.syntax]
> - define-compiler-syntax [chicken.syntax]
> - let-compiler-syntax [chicken.syntax]
Attached is a patch that makes it so. Only "ensure" has been removed
instead of moved to chicken.type (which was the wrong place for it
anyway; chicken.base would've been more suitable). We don't use it
anywhere in core and I don't think it's used much by eggs either.
After this patch is accepted and applied, we can move these macros
into the miscmacros egg (or maybe let eval-when fall by the wayside
because it's a weird CL concept that doesn't fit the Scheme model
very well, and can be replaced by cond-expand anyway)
Cheers,
Peter
0001-Move-remaining-macros-from-chicken-into-other-module.patch
Description: Text Data
signature.asc
Description: PGP signature