From: Per Bothner <per@bothner.com>
To: Emmanuel Oga <emmanueloga@gmail.com>, kawa@sourceware.org
Subject: Re: More internals documentation
Date: Sat, 10 Nov 2018 00:01:00 -0000 [thread overview]
Message-ID: <d6e4018d-ea77-8b53-a118-45b21efc7762@bothner.com> (raw)
In-Reply-To: <CAMsuM5oNWrQ65=ZaznN1C023JoEfgiXG-p335n0oXFeLAsXdhg@mail.gmail.com>
On 11/9/18 3:47 PM, Emmanuel Oga wrote:
> Hi,
>
> I found this excellent documentation:
>
> https://www.gnu.org/software/kawa/internals/index.html
>
> It mentions that it may be out of date (apparently the document is more or
> less exactly 10 years old!).
Actually, 20 years old, but it looks like the last update was 2009.
It could do with some work, but it's still a helpful overview.
> I was wondering if there are other complimentary docs or presentation I
> should watch to learn more about kawa implementation and in general how to
> compile scheme to java.
Not that I know. You can study the code, of course, but I'm sure
it can be a bit overwhelming.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2018-11-10 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 23:47 Emmanuel Oga
2018-11-10 0:01 ` Per Bothner [this message]
2018-11-10 1:50 ` Emmanuel Oga
2018-11-10 3:12 ` Per Bothner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d6e4018d-ea77-8b53-a118-45b21efc7762@bothner.com \
--to=per@bothner.com \
--cc=emmanueloga@gmail.com \
--cc=kawa@sourceware.org \
/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).