Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-07 Thread Jörg F. Wittenberger
Am 06.11.2013 21:21, schrieb Peter Bex: On Wed, Nov 06, 2013 at 08:50:05PM +0100, Jörg F. Wittenberger wrote: This second parameter is always vars, which in turn is the third parameter of make-mode-choice below. Are you sure it isn't already #unspecified where make-mode-choice is invoked?

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-07 Thread Peter Bex
On Thu, Nov 07, 2013 at 10:09:24AM +0100, Jörg F. Wittenberger wrote: And sure one level up there was the broken letrec, which when written as letrec* brings everything back to working order. Ah, that's good to hear. Sorry for the noise again. (Now I've got a different problem… rscheme is

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-07 Thread John Cowan
Jörg F. Wittenberger scripsit: (Now I've got a different problem… rscheme is still supposed to run this code. But I'm not inclined to add letrec* support to rscheme. :-/ ) You don't need to. Letrec* was born from the realization that many R5RS Schemes that were claiming to implement letrec

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-07 Thread Jörg F. Wittenberger
Thanks John, Am 07.11.2013 17:40, schrieb John Cowan: So for RScheme purposes, just write a trivial syntax-rules macro: (define-syntax letrec* (syntax-rules () ((letrec* . x) (letrec . x (This requires loading the RScheme syntax-rules support.) The main point for me is in your

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Hi, despite the fact that salmonella currently seems to be happy with the situation, let me add my €0,02. Sometimes the solution is not more code but less. Chicken's interrupt handling was broken for quite a long time. There is by now still a problem lurking and waiting to be triggered:

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 15:29, schrieb Peter Bex: On Wed, Nov 06, 2013 at 03:21:18PM +0100, Jörg F. Wittenberger wrote: My solution at that time was to coalesce signals by type and handle all reasons of a particular signal in a single signal handler (anyway) since - as you're pointing out - this must be

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 19:11, schrieb Peter Bex: On Wed, Nov 06, 2013 at 06:00:34PM +0100, Jörg F. Wittenberger wrote: Now I cam confused. True, there are 256 possible signal handlers in ##sys#signal-vector How could those be addressed/used at all? The timer interrupt signal has value 255. I'm sure

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Mario Domenech Goulart
Hi Jörg, On Wed, 06 Nov 2013 19:20:41 +0100 Jörg F. Wittenberger joerg.wittenber...@softeyes.net wrote: It's somehow related to code, which uses Petrofsky extraction (replacing some hon-hygienic macros I've been using before). This used to compile perfectly for several month. Now it

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 19:33, schrieb Mario Domenech Goulart: Hi Jörg, On Wed, 06 Nov 2013 19:20:41 +0100 Jörg F. Wittenberger joerg.wittenber...@softeyes.net wrote: It's somehow related to code, which uses Petrofsky extraction (replacing some hon-hygienic macros I've been using before). This used

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 19:35, schrieb Jörg F. Wittenberger: Am 06.11.2013 19:33, schrieb Mario Domenech Goulart: I'd bet it is a consequence of the introduction of `letrec*'. The behavior of `letrec' has been fixed with the introduction of `letrec*' (see

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Peter Bex
On Wed, Nov 06, 2013 at 07:20:41PM +0100, Jörg F. Wittenberger wrote: Now I ran a full recompile. To the effect that some macro expansion has been changed to the worse. It's somehow related to code, which uses Petrofsky extraction (replacing some hon-hygienic macros I've been using

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Peter Bex
On Wed, Nov 06, 2013 at 07:37:11PM +0100, Jörg F. Wittenberger wrote: I'm afraid it's something within the macro expander itself... which means that it might effect more code than just the one here. To that end: my code uses this syntax eventually in the context of a lambda. Maybe that's

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 19:35, schrieb Peter Bex: On Wed, Nov 06, 2013 at 07:20:41PM +0100, Jörg F. Wittenberger wrote: Now I ran a full recompile. To the effect that some macro expansion has been changed to the worse. It's somehow related to code, which uses Petrofsky extraction (replacing some

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Peter Bex
On Wed, Nov 06, 2013 at 07:39:06PM +0100, Jörg F. Wittenberger wrote: At the moment this is my favorite, where I'd bet things break: (define-syntax define-transformer (syntax-rules () ((_ transformer errloc body) (begin ;; (: name :render-renderer:) (define

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 19:39, schrieb Jörg F. Wittenberger: Am 06.11.2013 19:35, schrieb Peter Bex: On Wed, Nov 06, 2013 at 07:20:41PM +0100, Jörg F. Wittenberger wrote: Now I ran a full recompile. To the effect that some macro expansion has been changed to the worse. It's somehow related to code,

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 20:27, schrieb Peter Bex: On Wed, Nov 06, 2013 at 08:18:20PM +0100, Jörg F. Wittenberger wrote: Things seem to be much worse than expected. Without going into all the nasty details, this is roughly where the problem is: The parameter named 'static-variables' here turned out to

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 20:33, schrieb Jörg F. Wittenberger: Am 06.11.2013 20:27, schrieb Peter Bex: On Wed, Nov 06, 2013 at 08:18:20PM +0100, Jörg F. Wittenberger wrote: NAH; I don't expect you to dig into it. Actually it looks as if my assessment was wrong anyway: in the meantime I traced the

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Peter Bex
On Wed, Nov 06, 2013 at 08:34:38PM +0100, Jörg F. Wittenberger wrote: At least we're now within the scope of a letrec ;-) I must say that's a huge relief :) Cheers, Peter -- http://www.more-magic.net ___ Chicken-hackers mailing list

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-06 Thread Jörg F. Wittenberger
Am 06.11.2013 20:38, schrieb Peter Bex: On Wed, Nov 06, 2013 at 08:34:38PM +0100, Jörg F. Wittenberger wrote: At least we're now within the scope of a letrec ;-) I must say that's a huge relief :) I'm not that sure about the relief. For the fun of it (no more, except that somebody is

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-05 Thread Mario Domenech Goulart
On Tue, 5 Nov 2013 16:52:16 +0100 Peter Bex peter@xs4all.nl wrote: On Mon, Nov 04, 2013 at 10:09:54PM +, Mario Domenech Goulart wrote: On Mon, 4 Nov 2013 21:09:06 +0100 Peter Bex peter@xs4all.nl wrote: The patch's commit message explains it all :) I hope it's clear enough to

[Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-04 Thread Peter Bex
Hi all, The patch's commit message explains it all :) I hope it's clear enough to understand what's going on in the patch. If not, feel free to ask me for clarification. I hope I can provide it :/ I've added a few comments to the code again to explain what's happening, as that was REALLY

Re: [Chicken-hackers] [PATCH] Fix for #989 and hopefully #877 too

2013-11-04 Thread Mario Domenech Goulart
On Mon, 4 Nov 2013 21:09:06 +0100 Peter Bex peter@xs4all.nl wrote: The patch's commit message explains it all :) I hope it's clear enough to understand what's going on in the patch. If not, feel free to ask me for clarification. I hope I can provide it :/ I've added a few comments to