Noah Lavine writes:
> For instance, I think it's really important to be able to load modules
> written in
> other languages. However, this may be language-dependent to a certain extent,
> because
> some languages (Python) already have ways to define modules. In those cases
> we should
> stick
Ian Price writes:
> First, I'm going to try and write a proof-of-concept guile-elisp
> executable. This shouldn't be too hard, I think, and may shed some light
> on expected difficulties.
I was distracted by the pfds release so it's taken me longer than it
should have, but as expected, it wasn't
So, here's the "plan of attack" I'm envisioning for this.
Right now, questions of cross-language module referencing can be
ignored. I think it is mostly orthogonal to the current goal of running
non-scheme scripts.
First, I'm going to try and write a proof-of-concept guile-elisp
executable. This
As you say, the only real solution is to do more than one of these things.
For instance, I think it's really important to be able to load modules
written in other languages. However, this may be language-dependent to a
certain extent, because some languages (Python) already have ways to define
mod
As promised in the other thread, here is my list. This was really a
response to the even the earlier thread I started, which I
(unfortunately) didn't reply to at the time.
First off, they important question "why do we need this?". Well, guile
is a multi-language vm in principle, even if Scheme is
