As a first step it would be sufficient to find a way to automatically export the Gerbil standard library as a gambit module.
This would bring all the libraries to the wider gambit ecosystem, sans the macrology (which is a little harder to do).

-- vyzo

On Fri, Apr 10, 2020 at 11:19 PM Dimitris Vyzovitis <vyzo@hackzen.org> wrote:
I would wholeheartedly welcome such an initiative, and I would gladly help out anyone interested to take it on.
I am currently swamped with work (and will be for the forseeable future), so I can't do it on my own.

-- vyzo

On Fri, Apr 10, 2020 at 11:08 PM Marc Feeley <feeley@iro.umontreal.ca> wrote:

> On Apr 10, 2020, at 2:19 PM, Dimitris Vyzovitis <vyzo@hackzen.org> wrote:
>
> You might be interested in the gerbil socket library a spin; there is support for UNIX domain sockets through raw devices
>
> -- vyzo

It would be nice if that socket library was a Gambit module so that other Gambit users can use it!  :-)

In fact it would be great to have a way for (most) Gerbil modules to be directly accessible from pure Gambit code with an (import (gerbil xxx)) or something like that.  That would lessen the community split between Gerbil and pure Gambit users.

Something to consider is to turn Gerbil into a Gambit module so it can be installed directly using Gambit’s package manager.  This is already the model for Termite Scheme which was initially designed as a separate language but is now a Gambit module.  I’ve also approached Guillaume Cartier to turn JazzScheme into a Gambit module.  Note that I’m not talking about a builtin module, but rather a module hosted on its own git repository and installable with “gsi -install github.com/user/my-great-lang”.

If anyone is interested in contributing towards this goal, please let me know!

Marc