Re: [Chicken-users] macro systems and chicken (long)

2008-04-05 Thread Alaric Snell-Pym
On 4 Apr 2008, at 7:32 pm, John Cowan wrote: I suppose that syntax extension is one thing, arbitrary compile-time programming is another. It's useful to be able to express common patterns directly in the language, but I don't see the point of running code in the compiler, which is a rather

Re: [Chicken-users] macro systems and chicken (long)

2008-04-05 Thread Alex Shinn
John == John Cowan [EMAIL PROTECTED] writes: John Alaric Snell-Pym scripsit: Syntax-rules is handy for simple stuff, but I'd hate for it to be the only macro system I had - I like to think of it as a shorthand for a reasonably common case, TBH. John I think quite

Re: [Chicken-users] macro systems and chicken (long)

2008-04-05 Thread John Cowan
Alex Shinn scripsit: DEFINE-MACRO is just EVAL. Syntactic closures is just EVAL with the two extra env parameters, [...]. And as I believe I heard someone say on #scheme the other day, if your program involves EVAL, it's probably broken. Even if the EVAL is hidden behind something else. Et

[Chicken-users] srfi-18 and callbacks

2008-04-05 Thread Jim Ursetto
Let's say I have two callback handlers registered and within the handlers I do a thread-sleep! or thread-yield!. The C caller is the same for both (it's a busy handler), they are just invoked with different data. Now this sequence of events occurs: thread 1 enters the callback thread 2 enters