From: Andrew Cagney <cagney@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: cni vs jni
Date: Thu, 12 Jul 2007 13:57:00 -0000 [thread overview]
Message-ID: <46963159.30402@redhat.com> (raw)
In-Reply-To: <18069.3978.11236.967269@zebedee.pink>
How does BC (binary compatible abi) fit into all this?
(I know frysk's build system needs to be changed, but there are
compatibility issues?)
Andrew Haley wrote:
> Andrew Cagney writes:
> > [This was today's technical topic]
>
> > Possible options
> >
> > - simplistically translate the bindings into JNI
> >
> > - push more core code into C++ and move the bindings to a higher layer
> >
> > - status quo
>
> Or port CNI to Sun's Java. It's far from impossible, and as far as I
> an see the only real obstacle is getting buy-in from the GNU C++
> maintainers.
>
> Andrew.
>
>
next prev parent reply other threads:[~2007-07-12 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:03 Andrew Cagney
2007-07-11 17:12 ` Andrew Haley
2007-07-12 13:57 ` Andrew Cagney [this message]
2007-07-12 14:00 ` Andrew Haley
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=46963159.30402@redhat.com \
--to=cagney@redhat.com \
--cc=aph@redhat.com \
--cc=frysk@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).