Re: [Chicken-hackers] [PATCH] Adding iset to core and using it for Unicode-capable SRFI-14.

[Alex Shinn]

On Mon, Feb 4, 2013 at 5:58 AM, Felix <address@hidden> wrote:

>
> That's why I asked in advance what people wanted
> (is lib size or runtime memory or speed more important?),
> and since the only response I got was "could you provide
> a patch" I sent what I think is the best option.
>
> If we want to trim down the size, there's quite a lot that
> can be removed from iset.  Almost all of the bit-vector
> operations can be removed, and because of the odd way
> I defined those I believe that's taking up most of the
> space.

I want lib-size and speed, please.

Well, these are diametrically opposed, but right now

Chicken doesn't have either :)

If you want to optimize the core Chicken you probably

don't want to include huge APIs of rarely used procedures

as are found in srfi-1 and srfi-14.  You can just provide

the most common routines in extras.

For char-sets in particular, I've found that most users

are just clients, so chibi provides the (chibi char-set base)

library which defines only `char-set?' and `char-set-contains?'.

This is sufficient for srfi-13.  For people who really do want

to manipulate char-sets, srfi-14 can be provided as a separate

library.

Anyway, double checking the sizes, the object file for the

trimmed iset is only 25k bigger than the srfi-14 reference impl.

That's probably roughly what we'll recover from replacing

the irregex char-sets later (irregex just defines what it needs,

not all of srfi-14).

-- 

Alex