Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-17 Thread Felix Winkelmann
If the mini-srfi-1 stuff is only (to be) required in operator position it could be given as syntax. Right, depending on how much code is generated. Operators that don't include a loop are likely to be inlined by the compiler, anyway, who takes care of avoiding the duplication of values in

Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-17 Thread Jörg F. Wittenberger
Just a remark. If the mini-srfi-1 stuff is only (to be) required in operator position it could be given as syntax. Am 15.02.2015 um 23:44 schrieb Felix Winkelmann: - There is an include file (mini-srfi-1.scm) that holds the procedures that are currently needed. It is included by several

Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-15 Thread Felix Winkelmann
- There is an include file (mini-srfi-1.scm) that holds the procedures that are currently needed. It is included by several units, mostly compiler units. Rather than including the file, would it be better to construct mini-srfi-1 as another chicken.compiler library unit and link it with

Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-14 Thread Evan Hanson
On 2015-02-01 21:56, Felix Winkelmann wrote: I pushed a branch (drop-srfi-1) for extracting srfi-1 from chicken-core. I thought it might be easier to handle than a patch because I'm not sure if everybody agrees on the way it's been implemented, and some things may change. Fantastic! I'm very

Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-02 Thread John Cowan
Felix Winkelmann scripsit: Right, that was the intention. The definitions in mini-srfi-1.scm are not exposed currently. Oh, if they don't show through to user code in csi, then no problem. -- John Cowan http://www.ccil.org/~cowanco...@ccil.org Nobody expects the RESTifarian

Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-01 Thread John Cowan
Felix Winkelmann scripsit: - There is an include file (mini-srfi-1.scm) that holds the procedures that are currently needed. It is included by several units, mostly compiler units. This sounds like the Right Thing. We'll need some documentation on what mini-srfi-1 supports; in

[Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-01 Thread Felix Winkelmann
Hello! I pushed a branch (drop-srfi-1) for extracting srfi-1 from chicken-core. I thought it might be easier to handle than a patch because I'm not sure if everybody agrees on the way it's been implemented, and some things may change. Here a few notes: - There is an include file

Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-01 Thread Felix Winkelmann
From: Peter Bex pe...@more-magic.net Subject: Re: [Chicken-hackers] extracting srfi-1 from chicken 5 Date: Mon, 2 Feb 2015 08:27:38 +0100 On Sun, Feb 01, 2015 at 05:23:11PM -0500, John Cowan wrote: Felix Winkelmann scripsit: - There is an include file (mini-srfi-1.scm) that holds

Re: [Chicken-hackers] extracting srfi-1 from chicken 5

2015-02-01 Thread Peter Bex
On Sun, Feb 01, 2015 at 05:23:11PM -0500, John Cowan wrote: Felix Winkelmann scripsit: - There is an include file (mini-srfi-1.scm) that holds the procedures that are currently needed. It is included by several units, mostly compiler units. This sounds like the Right Thing. We'll