[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Chicken-users] reducing the size of chicken runtime
From: |
Peter Bex |
Subject: |
Re: [Chicken-users] reducing the size of chicken runtime |
Date: |
Thu, 19 Nov 2015 17:44:32 +0100 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
On Thu, Nov 19, 2015 at 08:36:43AM -0800, Dan Leslie wrote:
> Isn't there a significant barrier to determining what to strip due to eval,
> apply and read?
Only if you want to use those. Eval itself is in eval.scm,
which can be left out using -explicit-use, as mentioned in the
wiki page. Apply isn't a problem, it is very small and lives
in runtime.c. Read is rather large, but it's extendable, so
for example the #u8() syntax is only hooked in when you actually
load srfi-4 (which is also self-contained).
So there already is quite a bit of stuff you can leave out.
But if you do that, you might not be able to use any eggs, unless
you're very conservative about what you use.
Cheers,
Peter
signature.asc
Description: Digital signature