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

[Alex Shinn]

On Sun, Feb 3, 2013 at 11:36 PM, Peter Bex <address@hidden> wrote:

On Sat, Feb 02, 2013 at 06:10:25PM +0900, Alex Shinn wrote:
> Alternately we can drop iset and just define everything
> in terms of chars to begin with, but I think iset is useful.

Could you elaborate on this comment?  I don't understand what
you mean by "define everything in terms of chars".

iset manages integer sets.  The srfi-14 proposed

is a thin wrapper around iset, first translating chars to

integers.  We could alternately remove the integer

interface and just use chars for everything.

> The libchicken size on my machine is about 100k larger.
> This should be reclaimed after the next change which
> would redefine the irregex char-sets in terms of SRFI-14.
> The change after that defines the utf8 egg char-sets in
> terms of the core.

Why did you chose to import the entire iset egg?  It would
make more sense to migrate the cset stuff from irregex into
srfi-14 and change irregex to use srfi-14, wouldn't it?
This would mean less code, overall.

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.

-- 

Alex