From: "Hans Åberg" <haberg-1@telia.com>
To: Matt Wette <matt.wette@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: multi-lingual guile: language strictness
Date: Sat, 14 Jul 2018 21:09:08 +0200 [thread overview]
Message-ID: <15D46E91-0D20-451A-B73C-99209416F741@telia.com> (raw)
In-Reply-To: <5b7324d4-a50d-7278-4251-8005a5350214@gmail.com>
> On 14 Jul 2018, at 20:45, Matt Wette <matt.wette@gmail.com> wrote:
>
> On 07/14/2018 09:22 AM, Hans Åberg wrote:
>>> On 14 Jul 2018, at 15:53, William ML Leslie <william.leslie.ttg@gmail.com>
>>> wrote:
>>>
>>> On 14 July 2018 at 12:57, Brett Gilio
>>> <brettg@posteo.net>
>>> wrote:
>>>
>>>> Is this possibility for making Guile multi-lingual a promised feature,
>>>> or more of a wishlist type thing? I'll have to think about some ways
>>>> that might be good to approach this, because the limiting
>>>> volunteer-community is definitely going to be an issue.
>>>>
>>> It's already a thing.
>>>
>>> https://www.gnu.org/software/guile/manual/html_node/Other-Languages.html
>> Is it possible to call them at the same time, via the C interface?
>>
> I would think so. In general all languages see the same name space.
>
> scheme@(guile-user)> ,L ecmascript
> Happy hacking with ECMAScript! To switch back, type `,L scheme'.
> ecmascript@(guile-user)> function foo(x) { return x + 1; };
> ecmascript@(guile-user)> foo(1);
> $1 = 2
> ecmascript@(guile-user)> ,L scheme
> Happy hacking with Scheme! To switch back, type `,L ecmascript'.
> scheme@(guile-user)> (foo 1)
> $2 = 2
Yes, that is what I asked for, to be able to create objects in one language and interact with the same objects in another.
next prev parent reply other threads:[~2018-07-14 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 2:53 multi-lingual guile: language strictness Matt Wette
2018-07-14 2:57 ` Brett Gilio
2018-07-14 13:53 ` William ML Leslie
2018-07-14 16:22 ` Hans Åberg
2018-07-14 18:45 ` Matt Wette
2018-07-14 19:09 ` Hans Åberg [this message]
2018-07-14 19:24 ` Brett Gilio
2018-07-14 7:04 ` tomas
2018-07-14 13:49 ` William ML Leslie
2018-07-16 21:00 ` Hugo Hörnquist
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15D46E91-0D20-451A-B73C-99209416F741@telia.com \
--to=haberg-1@telia.com \
--cc=guile-devel@gnu.org \
--cc=matt.wette@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).