This is the mail archive of the java-discuss@sourceware.cygnus.com mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Proposal for CNI/JNI problems

To: Paul Fisher <pnfisher at redhat dot com>
Subject: Re: Proposal for CNI/JNI problems
From: "Aaron M. Renn" <arenn at urbanophile dot com>
Date: Wed, 12 Jan 2000 20:39:37 -0600
Cc: java-discuss at sourceware dot cygnus dot com, classpath at gnu dot org
Organization: GNU's Not Unix!
References: <y68k8lg6t70.fsf@ignucius.devel.redhat.com> <m24scjx2hi.fsf@magnus.bothner.com> <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/

Follow-Ups:
- Re: Proposal for CNI/JNI problems
  - From: Stuart Ballard

References:
- Proposal for CNI/JNI problems
  - From: Paul Fisher
- Re: Proposal for CNI/JNI problems
  - From: Per Bothner
- Re: Proposal for CNI/JNI problems
  - From: Paul Fisher

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]