Re: [caplisp-devel] httpsy porting

[David M. <ra...@gm...>]

Sorry for the very delayed replay, 3 math classes at once has been
more of a load than I thought it would! Comments interspersed below.=20
-David Mercer

On 9/27/05, James Graves <an...@xn...> wrote:
>
> I got the good word from the Scheme 48 folks.  I'm not going to bother
> with SWIG at this point.  It would be difficult to add support for
> another target.  In fact, though I thought it was the case, there is no
> support in SWIG for any CL implementation either.  :-(

I'm actually kinda glad you're back to s48 for your efforts, as that's
a direction I'd wanted to explore for a while, too. Even emailed jar
about some things regarding such an effort a time or two.   I punted
to image level confinement in my current caplisp aspirations for
pretty much the reasons jar outlined in very good detail in your
message (on elang I think) recently.  Or at least a decent subset of
them!

> So we've got some other tools to do the FFI generation for OpenSSL
> and/or GNU TLS.  I'm only going to need a small part of the API to begin
> with anyway.

That sounds like a great place to start.

> I'm also tempted to work on some kind of tool to automatically convert
> modules for other Schemes (most notably Chicken and DrScheme) to make it
> easier to import their libraries.  I'll need to hand-convert a few
> first, to get a good feel for what that would require.

Oh such a tool would be very, very sweet!

I'd actually started a reply to your longish email I referred to
above, but realized it would be mostly just "yes, I agree" type
statements; hence this one instead.

I'm very interested to follow any/all progress you make with s48.  Let
us all know when there's code to look at!

Cheers,

David Mercer
Tucson, AZ