[Chicken-users] Porting eggs to Chicken 5

[Sven Hartrumpf]

Hi.

I am trying to port some of my code from Chicken 4 to 5.
Is there a small guide how to port an egg from 4 to 5?
Is there a wish list or popularity list for eggs
to be ported?

Ciao
Sven

[Christian Kellermann]

Post by Sven Hartrumpf
Hi.
I am trying to port some of my code from Chicken 4 to 5.
Is there a small guide how to port an egg from 4 to 5?
Is there a wish list or popularity list for eggs
to be ported?

There is the wiki page at
https://wiki.call-cc.org/porting-c4-to-c5

We will handle this just like the shift from 3->4. Port what you
need, the rest is abandonware anyway until someone asks for it...

Kind regards,

Christian

[Sven Hartrumpf]

Hi Christian.

Post by Christian Kellermann

Post by Sven Hartrumpf
Hi.
I am trying to port some of my code from Chicken 4 to 5.
Is there a small guide how to port an egg from 4 to 5?
Is there a wish list or popularity list for eggs
to be ported?

There is the wiki page at
https://wiki.call-cc.org/porting-c4-to-c5

Thanks. This helped a lot.
There are many C library bindings relying on easyffi.
Are there any plans to port the easyffi egg?

Ciao
Sven

[Peter Bex]

Post by Sven Hartrumpf
Thanks. This helped a lot.
There are many C library bindings relying on easyffi.
Are there any plans to port the easyffi egg?

This is one of those eggs that should really be left in the dust as
things are moved to the new CHICKEN. Bind is the supported and
maintained way of doing FFI in an easier way than the core.

Also, if at all possible, I'd argue to use the core FFI, to reduce
dependencies.

Can you give some examples of eggs that use easyffi where it's hard
to convert them to bind or core FFI?

Cheers,
Peter

[Sven Hartrumpf]

Hi Peter.

Post by Peter Bex

Post by Sven Hartrumpf
Thanks. This helped a lot.
There are many C library bindings relying on easyffi.
Are there any plans to port the easyffi egg?

This is one of those eggs that should really be left in the dust as
things are moved to the new CHICKEN. Bind is the supported and
maintained way of doing FFI in an easier way than the core.

Now I remember to have read this before, sorry.

Post by Peter Bex
Also, if at all possible, I'd argue to use the core FFI, to reduce
dependencies.
Can you give some examples of eggs that use easyffi where it's hard
to convert them to bind or core FFI?

No, I was just lazy when porting an egg that relied on easyffi.
I will follow your advice now and report if I run into trouble.

Ciao
Sven