New egg: SRFI-130: Cursor-based string library

I would like to submit a new egg for publication: SRFI-130: Cursor-based string library The documentation is here: [1] The release-info is here: [2] and test-new-egg has given it a clean bill of health. --Sergey [1] - https://wiki.call-cc.org/eggref/5/srfi-130 [2] -

SRFI-60 (Integers as Bits) ported from Chicken 4 to 5

I just ported SRFI-60 (Integers as Bits) from Chicken 4 to 5 and would like to submit it for publication. Its documentation can be found here: [1] Its release-info is here: [2] and test-new-egg gives is a clean bill of health. --Sergey [1] - https://wiki.call-cc.org/eggref/5/srfi-60 [2] -

SRFI-38 ported from Chicken 4 to 5

I just ported the SRFI-38 egg from Chicken 4 to 5, and would like to submit it for publication. The Chicken 5 documentation (copied verbatim from the Chicken 4 egg) is here: [1] The release-info file is here: [2] A run of test-new-egg reported that the "Egg looks ok". --Sergey [1] -

New egg: SRFI-35

I just created a new egg for SRFI-35, and would like to submit it for publication. Its documentation is here: [1] Its release-info is here: [2] I've ran test-new-egg on it, and it reported that the "Egg looks ok" --Sergey [1] - https://wiki.call-cc.org/eggref/5/srfi-35 [2] -

Re: Some questions about concurrency (mostly)

> 1. Are there any problems with creating a condition (as in exception, >not srfi-18 condition variable) in one thread and raising it in one >or more other threads? No problem here, I'd say, data can be freely exchanged between threads, since they share a global address space. A condition

Re: Some questions about concurrency (mostly)

Am Thu, 05 Nov 2020 23:22:09 +0100 schrieb Fredrik Appelberg : > 3. I'm new to dynamic-wind. If I wanted to create a general form for >executing a thunk protected by a mutex, would this be a good idea? > > (define (with-lock mutex thunk) >(dynamic-wind >(lambda ()

Re: Some questions about concurrency (mostly)

felix.winkelm...@bevuta.com writes: Hi, and thanks for the reply :) >> 1. Are there any problems with creating a condition (as in exception, >>not srfi-18 condition variable) in one thread and raising it in one >>or more other threads? > > No problem here, I'd say, data can be freely

Re: New egg: SRFI-35

On Fri, 06 Nov 2020 00:30:18 -0800 noosph...@mailc.net wrote: > I just created a new egg for SRFI-35, and would like to submit it for > publication. > > Its documentation is here: [1] > > Its release-info is here: [2] > > I've ran test-new-egg on it, and it reported that the "Egg looks ok" > >

Re: Some questions about concurrency (mostly)

> I'm not doing any call/cc or non-local exit shenanigans, but the code > uses srfi-18 threads and does I/O over TCP. As I understand it, srfi-18 > is implemented using continuations. Will that cause problems with my > with-lock function? I'm thinking that a thread that has aquired the lock > in

Re: Some questions about concurrency (mostly)

Am Fri, 06 Nov 2020 17:48:26 +0100 schrieb felix.winkelm...@bevuta.com: > > I'm not doing any call/cc or non-local exit shenanigans, but the > > code uses srfi-18 threads and does I/O over TCP. As I understand > > it, srfi-18 is implemented using continuations. Will that cause > > problems with

New egg: SRFI-152

I'd like to submit for publication a new egg: SRFI-152 Its documentation is here: [1] The release-info is here: [2] test-new-egg gives it a clean bill of health. Thanks to everyone on #chicken for helping me to solve some tricky issues during the porting process of this egg! --Sergey

Re: New egg: SRFI-152

On Fri, 06 Nov 2020 13:29:13 -0800 noosph...@mailc.net wrote: > I'd like to submit for publication a new egg: SRFI-152 > > Its documentation is here: [1] > > The release-info is here: [2] > > test-new-egg gives it a clean bill of health. > > Thanks to everyone on #chicken for helping me to