Re: continuation-mark-set->iterator

2022-11-14 Thread Marc Nieper-Wißkirchen
Thank you! Am Di., 15. Nov. 2022 um 00:02 Uhr schrieb Shiro Kawai : > > It says "Returns ... constructed by continuation-mark-set->list when applied > to the same arguments", but continuation-mark-set->iterator takes key-list, > while continuation-mark-set->list takes a single key. Reference >

continuation-mark-set->iterator

2022-11-14 Thread Shiro Kawai
It says "Returns ... constructed by continuation-mark-set->list when applied to the same arguments", but continuation-mark-set->iterator takes key-list, while continuation-mark-set->list takes a single key. Reference implementation suggests it is intended to be continuation-mark-set->list*. If th

Re: Recent additions/changes (see personal repo)

2022-11-14 Thread Marc Nieper-Wißkirchen
Thanks for taking a closer look at the recent changes! Am Mo., 14. Nov. 2022 um 20:05 Uhr schrieb Shiro Kawai : > > POSIX does not require pthread_cond_wait to be interrupted by a signal; It > does call a signal handler but can resume waiting, instead of returning to > the caller as most other

Re: Recent additions/changes (see personal repo)

2022-11-14 Thread Shiro Kawai
POSIX does not require pthread_cond_wait to be interrupted by a signal; It does call a signal handler but can resume waiting, instead of returning to the caller as most other system calls. That makes implementing Schemel-evel thread-interrupt! difficult. In Gauche, a Unix signal handler just re