Re: New egg for SRFI 193: Command line

Hi Lassi, On Fri, 23 Oct 2020 19:35:54 +0300 Lassi Kortela wrote: > You wrote test-new-egg and a ton of other stuff. Thank you for all > your efforts for Scheme; Chicken's infrastructure works really well! That's very nice of you. Thanks for your kind words. Really appreciated. All the best.

Re: New egg for SRFI 193: Command line

Thanks for your contributions to CHICKEN. No problem, sorry for taking so long! You can edit the wiki anonymously, but since you are maintaining eggs, I'd highly recommend using a personal wiki account (reason being every time we see an anonymous edit we must check whether it is spam or not).

Re: New egg for SRFI 193: Command line

Hi Lassi, On Fri, 23 Oct 2020 13:08:51 +0300 Lassi Kortela wrote: >> Everything seems to be in order, I’ve added the egg to the repository! :) > > Thank you very much. > > Unfortunately it has a bug (my fault): chicken-install pre-compiles it > into a .so and (import (srfi 193)) in csi loads

Re: New egg for SRFI 193: Command line

> Is there a way to figure out if running in csi at runtime without using > cond-expand? > You can test "(feature? #:csi)" to figure out whether the current executable is "csi". felix

Re: New egg for SRFI 193: Command line

Everything seems to be in order, I’ve added the egg to the repository! :) Thank you very much. Unfortunately it has a bug (my fault): chicken-install pre-compiles it into a .so and (import (srfi 193)) in csi loads that .so instead of loading the source .scm file. The library uses cond-expand

Re: New egg for SRFI 193: Command line

Lassi Kortela wrote: > Based on the code posted to chicken-hackers previously, here's an egg > for SRFI 193: . > > test-new-egg says: > > < srfi-193 (1 of 1) >Fetching[ ok ] 0s >Reading

New egg for SRFI 193: Command line

Based on the code posted to chicken-hackers previously, here's an egg for SRFI 193: . test-new-egg says: < srfi-193 (1 of 1) Fetching[ ok ] 0s Reading .egg[ ok ]