From: Per Bothner <per@bothner.com>
To: "Germán Arias" <germanandre@gmx.es>, Kawa <kawa@sourceware.org>
Subject: Re: Approach to add a new language
Date: Thu, 24 Sep 2015 19:20:00 -0000 [thread overview]
Message-ID: <56044CD1.2050802@bothner.com> (raw)
In-Reply-To: <1443119328.2480.4.camel@german-HP-245-G2-Notebook-PC>
On 09/24/2015 11:28 AM, Germán Arias wrote:
> Hi all, I'm new at Kawa, although I have some experience in scheme, but
> not in java. I read that Kawa can be used to implement other programming
> languages in java platform. So I would like hear your suggestions to do
> this. I'm thinking on implement Objective-C, but I don't know how this
> works. Parse the objective-C files to generate the corresponding Sheme
> files is enough? Or is necessary other considerations? Thanks in advance
> for your help.
Objective-C might be a challenge on the JVM, partly because C is a challenge
on the JVM. Plus you have to define a mapping from the Objective-C class/object
model to the Java model.
Perhaps you could implement a subset of Objective-C - but why?
I wouldn't use Scheme as an intermediate language (though one could).
One problem is that makes it hard to get line number information correct.
Better (and faster) to parse Objective-C and generate the Expression
objects that Kawa uses.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2015-09-24 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 18:29 Germán Arias
2015-09-24 19:20 ` Per Bothner [this message]
2015-09-25 9:04 ` packaging classes in kawa Damien Mattei
2015-09-25 9:09 ` Damien Mattei
[not found] ` <CAE4XeMCHZVDNEMeHXbBHvsgtUXTTzqknZxuTyWp0og8BWuC_mQ@mail.gmail.com>
2015-09-25 13:10 ` Damien Mattei
2015-09-25 15:15 ` Per Bothner
2015-09-25 15:49 ` Damien Mattei
2015-09-25 16:21 ` Per Bothner
2015-09-26 3:41 ` Approach to add a new language Germán Arias
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=56044CD1.2050802@bothner.com \
--to=per@bothner.com \
--cc=germanandre@gmx.es \
--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).