[Chicken-users] SRFI-123 ported to Chicken 5

[Diego]

I've ported SRFI-123 to C5: https://github.com/dieggsy/srfi-123

I also made some minor fixes to lingering issues I hadn't yet cleaned up.

A couple questions:

- Is there a way to make a wiki entry for the egg in the egg repo itself? I'd 
rather version control something like that rather than edit with the web 
interface.

- How do I go about aliasing srfi.123 to srfi-123?


Diego



___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Back from the dead: pstk

[ipcore]

Hello John,

I considered doing this, but decided it would be a good idea to start 
with a clean slate. Wasn't 100% sure though, that's why I explicitly 
mentioned it.


If the general opinion is that history from SVN should be preserved, 
then I'll do that of course. So what do you folks think?


Best wishes,
-Heinz

On 2/26/19 3:04 PM, John Cowan wrote:

If it's not too hard, you might want to extract your changes from your new
git repo, drop the repo, use reposurgeon (a general VCS converter and
editor), and reapply your changes.  That way the history is preserved and
you don't need multiple repos.

On Tue, Feb 26, 2019 at 8:49 AM  wrote:


Hello,

As promised, I've ported the pstk egg to Chicken 5, and would like to
take over as maintainer.

https://github.com/utz82/pstk
https://raw.githubusercontent.com/utz82/pstk/master/pstk.release-info

License has been reverted to BSD 2-clause, as the main source actually
never was in the public domain.

I threw out the SVN backlog when importing to git, so maybe the C4 egg
should continue to use the old SVN repository instead. Otherwise pstk
should replace Chicken/Tk as the "maintained" Tk egg at this point. I do
plan on maintaining both 4 and 5 versions, in any case.

Haven't done any changes to the code for now, other than C5
compatibility tweaks, and setting default tclsh to tclsh8.6. I'm amazed
that this decade-old code works on C5 pretty much out of the box.

Best wishes,
-Heinz

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users





___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Back from the dead: pstk

[ipcore]

Hello Vasilij,

Good point, I'll add the documentation to the repo.

Regarding using the parens syntax for imports, that's good to know as 
well. I'm generally a fan of avoiding syntactic sugar that uses symbol 
characters, but I thought the dotted syntax was kind of neat.


There are some portable versions of pstk floating around on the web, so 
I think portability is not a major concern for the egg code. But it 
can't hurt either ;) So I'll change it in the next release.


Thanks a lot for your input, in any case!

Best wishes,
-Heinz


On 2/26/19 3:04 PM, Vasilij Schneidermann wrote:

Hello Heinz,


I threw out the SVN backlog when importing to git, so maybe the C4 egg
should continue to use the old SVN repository instead. Otherwise pstk should
replace Chicken/Tk as the "maintained" Tk egg at this point. I do plan on
maintaining both 4 and 5 versions, in any case.


This reminds me of one more thing, the tk egg has surprisingly useful
HTML documentation and includes a beginner's tutorial.  Currently it's
hosted at  and can be
used with the pstk egg as well.  Perhaps you might want to include it
into your repository as well?

Vasilij



___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Back from the dead: pstk

[Vasilij Schneidermann]

Hey Heinz,

> Haven't done any changes to the code for now, other than C5 compatibility
> tweaks, and setting default tclsh to tclsh8.6. I'm amazed that this
> decade-old code works on C5 pretty much out of the box.

Looks good.  One thing you might want to fix: C5 uses a R7RS-style
organization for core modules, so code like `(import (chicken base))`
maps to `(import chicken.base)` and `(import (srfi 1))` to `(import
srfi.1)` (which itself is an alias to `srfi-1` apparently).  The exact
mapping behind the scenes is more of an implementation detail, for this
reason I prefer the version with more parentheses.  It also helps with
compatibility, in case you ever want to write code running on more than
one Scheme implementation.

Vasilij


signature.asc
Description: PGP signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Back from the dead: pstk

[John Cowan]

If it's not too hard, you might want to extract your changes from your new
git repo, drop the repo, use reposurgeon (a general VCS converter and
editor), and reapply your changes.  That way the history is preserved and
you don't need multiple repos.

On Tue, Feb 26, 2019 at 8:49 AM  wrote:

> Hello,
>
> As promised, I've ported the pstk egg to Chicken 5, and would like to
> take over as maintainer.
>
> https://github.com/utz82/pstk
> https://raw.githubusercontent.com/utz82/pstk/master/pstk.release-info
>
> License has been reverted to BSD 2-clause, as the main source actually
> never was in the public domain.
>
> I threw out the SVN backlog when importing to git, so maybe the C4 egg
> should continue to use the old SVN repository instead. Otherwise pstk
> should replace Chicken/Tk as the "maintained" Tk egg at this point. I do
> plan on maintaining both 4 and 5 versions, in any case.
>
> Haven't done any changes to the code for now, other than C5
> compatibility tweaks, and setting default tclsh to tclsh8.6. I'm amazed
> that this decade-old code works on C5 pretty much out of the box.
>
> Best wishes,
> -Heinz
>
> ___
> Chicken-users mailing list
> Chicken-users@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/chicken-users
>
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

Re: [Chicken-users] Back from the dead: pstk

[Vasilij Schneidermann]

Hello Heinz,

> I threw out the SVN backlog when importing to git, so maybe the C4 egg
> should continue to use the old SVN repository instead. Otherwise pstk should
> replace Chicken/Tk as the "maintained" Tk egg at this point. I do plan on
> maintaining both 4 and 5 versions, in any case.

This reminds me of one more thing, the tk egg has surprisingly useful
HTML documentation and includes a beginner's tutorial.  Currently it's
hosted at  and can be
used with the pstk egg as well.  Perhaps you might want to include it
into your repository as well?

Vasilij


signature.asc
Description: PGP signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users

[Chicken-users] Back from the dead: pstk

[ipcore]

Hello,

As promised, I've ported the pstk egg to Chicken 5, and would like to 
take over as maintainer.


https://github.com/utz82/pstk
https://raw.githubusercontent.com/utz82/pstk/master/pstk.release-info

License has been reverted to BSD 2-clause, as the main source actually 
never was in the public domain.


I threw out the SVN backlog when importing to git, so maybe the C4 egg 
should continue to use the old SVN repository instead. Otherwise pstk 
should replace Chicken/Tk as the "maintained" Tk egg at this point. I do 
plan on maintaining both 4 and 5 versions, in any case.


Haven't done any changes to the code for now, other than C5 
compatibility tweaks, and setting default tclsh to tclsh8.6. I'm amazed 
that this decade-old code works on C5 pretty much out of the box.


Best wishes,
-Heinz

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users