From: "Aaron M. Renn" <arenn@urbanophile.com>
To: Paul Fisher <pnfisher@redhat.com>
Cc: java-discuss@sourceware.cygnus.com, classpath@gnu.org
Subject: Re: Proposal for CNI/JNI problems
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <20000112203937.D10725@urbanophile.com> (raw)
In-Reply-To: <y683ds36mi0.fsf@ignucius.devel.redhat.com>
Paul Fisher (pnfisher@redhat.com) wrote:
> > (1) Is it OK to write Classpath in C++ rather than C?
>
> Yes.
>
> > (2) Is it OK for Classpath to depend on G++ extensions?
>
> Yes.
I think this should be considered very carefully. I would like to avoid
these dependencies if possible. Particularly any dependencies on gcc.
Personally, it looks like in the core classes there will be so little
code that the JNI/CNI thing could be handled with #ifdef CNI/JNI and
a configure time option added to enable it. Or a set of macros might
handled almost everything reasonably well.
--
Aaron M. Renn (arenn@urbanophile.com) http://www.urbanophile.com/arenn/
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-01 0:00 Paul Fisher
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Bernd Kreimeier
2000-04-01 0:00 ` Alexandre Oliva
2000-04-01 0:00 ` Paul Fisher
2000-04-01 0:00 ` Aaron M. Renn [this message]
2000-04-01 0:00 ` Stuart Ballard
2000-04-01 0:00 ` Chris Blizzard
2000-04-01 0:00 ` Chris Blizzard
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Jochen Hoenicke
2000-04-01 0:00 ` Per Bothner
2000-04-01 0:00 ` Stuart Ballard
2000-04-01 0:00 ` Jon Olson
2000-04-01 0:00 Boehm, Hans
2000-04-01 0:00 Lam.Mark
2000-04-01 0:00 ` Aaron M. Renn
2000-04-01 0:00 ` Brian Jones
2000-04-01 0:00 David Pettersson
2000-04-01 0:00 ` 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=20000112203937.D10725@urbanophile.com \
--to=arenn@urbanophile.com \
--cc=classpath@gnu.org \
--cc=java-discuss@sourceware.cygnus.com \
--cc=pnfisher@redhat.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).