Re: SRFI-144 - initial port
Hi Diego, On Sun, 18 Apr 2021 19:40:47 + Diego wrote: > I've created an initial port of SRFI-144 that passes test-new-egg with > release-info here: > > https://code.dieggsy.com/srfi-144/plain/srfi-144.release-info > > I'm thinking a next step might be to test the procedures with C > equivalents in CHICKEN and see if it'd be best to switch to > those. Currently, only the two procedures stated in the SRFI document > are using the FFI, but I'm not sure if the claims made about Larceny > hold for us as well. Thanks. Your egg has been added to the coop. When you have a chance, please consider writing a wiki page for it. All the best. Mario -- http://parenteses.org/mario
SRFI-144 - initial port
Hi all, I've created an initial port of SRFI-144 that passes test-new-egg with release-info here: https://code.dieggsy.com/srfi-144/plain/srfi-144.release-info I'm thinking a next step might be to test the procedures with C equivalents in CHICKEN and see if it'd be best to switch to those. Currently, only the two procedures stated in the SRFI document are using the FFI, but I'm not sure if the claims made about Larceny hold for us as well. - Diego
Re: New egg (json-rpc) and some words about LSP
Hi Diego, Am 18.04.2021 01:45 schrieb Diego: Even beyond that though, chicken-doc doesn't actually seem to have a notion of modules at all - only egg names. So in any case it would be listed as (r7rs string-map). It might be worthwhile to look into adding module introspection to chicken-doc in the future... Thanks for the clarification, I wasn't aware of that. The way it is will make some documentation unreacheable, since I'm collecting symbols with apropos, which gives their modules. Is there an API for finding out which egg installed a specific module? If not, I see that `chicken-status -c` delivers a list containing the information I need, I can process that on startup and build a hash-table. Best regards, Ricardo
