[Top][All Lists]

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

Re: [Chicken-hackers] [PATCH][for chicken-5] Remove srfi-13

From: Peter Bex
Subject: Re: [Chicken-hackers] [PATCH][for chicken-5] Remove srfi-13
Date: Thu, 11 Sep 2014 15:44:34 +0200
User-agent: Mutt/

On Thu, Sep 11, 2014 at 03:25:24PM +0200, Felix Winkelmann wrote:
> Ah, well done, Mario! 
> But, some remarks:
> * Perhaps we should "svn cp" the release/4 branch and add new eggs
>   afterwards, otherwise the "5" directory will be in the way. By
>   copying the tree, the new eggs for the functionality extracted in
>   the recent CR will be available, too.

I don't grok what you are saying here.  Do you want to copy the entire
CHICKEN 4 egg list to CHICKEN 5?  It may be better to copy individual
eggs later, when we've finished all our module refactorings.  That way,
the eggs won't all break at once, and only the eggs people are really
interested in will survive the transition.

> * Wouldn't it be preferrable if we collect re-implementations of some
>   srfi-13 routines in a common library unit, for internal use only?

Maybe not just for internal use.  Perhaps a chicken.string module could
contain these things plus the CHICKEN-specific ones from data-structures,
like string-intersperse and such?  these functions are useful to user
code, too.  Especially if we optimise them by removing all the silly
polymorphisms from the SRFI-13 implementation.

> * Does this require a change-request? We haven't "officially" decided
>   yet on extracting the srfi's, even though it seems to be the
>   consensus.

Nah, CHICKEN 5 will break backwards compat across the board anyway, so
change-requests aren't really necessary.  If someone disagrees, they
can object here on the list.


reply via email to

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