Hi all, there is a problem I have with ticket 1231. http://bugs.call-cc.org/ticket/1231
In short: I'd love to see the patch applied. (Or learn about issues it causes.) Long story: The pigeon-hole egg I recently published looks internally somewhat like the "rewrite it using condition-variables" the source of the mailbox egg suggests. (Ignoring here that it allows for flow control to avoid a fast sender bringing down the whole system by blowing up memory consumption.) Right now the development version (according to the measurements I've been able to create - you know "benchmarks", they always lie) is roughly on par on performance with the mailbox egg. That is: WHEN using `(mutex-lock! #f #f)`. I hesitate to release this code, because I don't want to cause trouble. The released version works around the srfi-18 incompatibility at the cost of ~20% performance loss. Too bad to be ignored. Best /Jörg _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/chicken-users