Thanks Mario.
I just checked. The Scheduler code I'm using does not have this bug.
On Sep 29 2011, Mario Domenech Goulart wrote:
Hi Jörg,
On 29 Sep 2011 13:11:49 +0200 Jörg F. Wittenberger
joerg.wittenber...@softeyes.net wrote:
Recently (maybe 4.7.3 or .4) I'm seeing missbehavior from
The sandbox egg makes a call to the runtime.c procedure:
C_emit_trace_info
In commit 2d5244dd01d4e91ed6f73bb566e92f04a2ab6361 of core,
this procedure was deprecated in favor of:
C_emit_eval_trace_info
C_emit_syntax_trace_info
Below is the patch bringing the sandbox egg up-to-date
Patch looks good to me but should be ACKed by the egg author (Felix)
On Oct 1, 2011, at 5:01 PM, Alan Post wrote:
The sandbox egg makes a call to the runtime.c procedure:
C_emit_trace_info
In commit 2d5244dd01d4e91ed6f73bb566e92f04a2ab6361 of core,
this procedure was deprecated in favor
Nevermind. chicken-setup -f puts the egg in /tmp, not in the local dir. I
have the source and it seems to compile fine in 4.7.0
On Sat, Oct 1, 2011 at 9:23 PM, Matt Welland estifo...@gmail.com wrote:
Also, docs seem to be missing from the chicken 3 eggs pages and I could not
download the
