Re: New egg for SRFI 193: Command line

2020-10-23 Thread Mario Domenech Goulart
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.
Mario
-- 
http://parenteses.org/mario



Re: New egg for SRFI 193: Command line

2020-10-23 Thread Lassi Kortela

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).

To get an account, please send me a private message with the username
you want to use and the hash of your password.  It can be generated
with:

 $ openssl passwd -apr1


OK: lassik and $apr1$12JSSXLI$h0R26idN83V9EsUJTcHtF/


All the best.
Mario


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!




Re: New egg for SRFI 193: Command line

2020-10-23 Thread Mario Domenech Goulart
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 that .so instead of
> loading the source .scm file. The library uses cond-expand to figure
> out whether it's being loaded from csi or csc, but that doesn't work
> since csc has already expanded it when compiling the .so.
>
> Is there a way to figure out if running in csi at runtime without
> using cond-expand?
>
> The offending cond-expands are on this line:
> 
>
> and this line:
> 
>
>> The wiki page looks fine too, please upload it to the wiki when you have the 
>> time.
>
> I don't have an account to edit the wiki.

Thanks for your contributions to CHICKEN.

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).

To get an account, please send me a private message with the username
you want to use and the hash of your password.  It can be generated
with:

$ openssl passwd -apr1

All the best.
Mario
-- 
http://parenteses.org/mario



Re: New egg for SRFI 193: Command line

2020-10-23 Thread felix . winkelmann
> 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

2020-10-23 Thread Lassi Kortela

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 to figure out 
whether it's being loaded from csi or csc, but that doesn't work since 
csc has already expanded it when compiling the .so.


Is there a way to figure out if running in csi at runtime without using 
cond-expand?


The offending cond-expands are on this line: 



and this line: 




The wiki page looks fine too, please upload it to the wiki when you have the 
time.


I don't have an account to edit the wiki.



Re: New egg for SRFI 193: Command line

2020-10-23 Thread kooda
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 .egg[ ok ] 0s
>Checking dependencies...[ ok ] 0s
>Checking category...[ ok ] 0s
>Checking license[ ok ] 0s
>Checking author.[ ok ] 0s
>Installing..[ ok ] 1s
>Checking version[ -- ]
>Testing.[ ok ] 12s
>Checking documentation..[fail] 0s
> 
> An attempt at a wiki page is here: 
> .
> 
> Is this enough to go on? Let me know if more work is needed.

Everything seems to be in order, I’ve added the egg to the repository! :)
The wiki page looks fine too, please upload it to the wiki when you have the 
time.