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

2014-09-11 Thread Felix Winkelmann
From: Mario Domenech Goulart mario.goul...@gmail.com Subject: [Chicken-hackers] [PATCH][for chicken-5] Remove srfi-13 Date: Thu, 11 Sep 2014 12:37:24 + Hi, I'm not sure if it is the right moment for this kind of patch, but attached is one that removes srfi-13 from the core. I've made

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

2014-09-11 Thread Peter Bex
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

[Chicken-hackers] Master has been merged into chicken-5 branch

2014-09-11 Thread Christian Kellermann
Hi hackers, I have just merged the last master commits into chicken-5. The idea is that we will do a final 4.10 release and then continue to work on the chicken-5 branch which could be merged back into master then. So for newer patches you should base them on the chicken-5 branch. Bugfixes worth

Re: [Chicken-hackers] Master has been merged into chicken-5 branch

2014-09-11 Thread Christian Kellermann
* Mario Domenech Goulart mario.goul...@gmail.com [140911 16:20]: 4.x) and merging them into chicken-5. The rationale for this is: * We have a long road to CHICKEN 5 * CHICKEN 5 will be smaller, with less code, so it's easier to target CHICKEN 4 and remove code that don't apply to

Re: [Chicken-hackers] Master has been merged into chicken-5 branch

2014-09-11 Thread Mario Domenech Goulart
Hi Christian, On Thu, 11 Sep 2014 15:59:53 +0200 Christian Kellermann ck...@pestilenz.org wrote: I have just merged the last master commits into chicken-5. Many thanks for doing that. The idea is that we will do a final 4.10 release and then continue to work on the chicken-5 branch which

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

2014-09-11 Thread Peter Bex
On Thu, Sep 11, 2014 at 05:13:48PM +0200, Felix Winkelmann wrote: [replying to Peter] 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.

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

2014-09-11 Thread Felix Winkelmann
They'll still have to be ported one-by-one, as probably every egg will break. I still think moving the eggs en-masse gives us a better overview, otherwise we will just forget some eggs. And we can always delete eggs for which *everybody* agrees that they should go. As you know, one of the

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

2014-09-11 Thread John Cowan
Peter Bex scripsit: As you know, one of the problems with SRFI-13 is that it's extremely inefficient. It would make sense if user code can also rely on faster alternatives. One of the rules of CHICKEN optimization has long been to avoid SRFI-13 if you can. Other than the polymorphism

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

2014-09-11 Thread Felix Winkelmann
From: Oleg Kolosov bazur...@gmail.com Subject: Re: [Chicken-hackers] [PATCH][for chicken-5] Remove srfi-13 Date: Thu, 11 Sep 2014 21:51:27 +0400 On 09/11/14 20:45, Felix Winkelmann wrote: I don't see how providing faster alternatives to SRFI-13 procedures is mutually exclusive with making a