Re: [cdt-dev] JNI support

[Jeffrey Dever <jsdever@xxxxxxxxxxxx>]

Stepping from the java debugger to the C debugger and back would be the 
ultimate.  I'll put that on the features list but it will be some time 
before I get to that level of integration.

Ed Burnette wrote:

> This would be useful to us if we could step in the debugger from Java code into JNI C code and vice-versa. Seems like it should be part of CDT and not independent. It would be easier to develop independently at first if CDT was extensible enough (i.e., had the right extension points and public APIs) but I don't know if that's the case.
>
>
>  
>
> > -----Original Message-----
> > Date: Thu, 24 Apr 2003 00:16:25 -0400
> > From: Jeffrey Dever <jsdever@xxxxxxxxxxxx>
> > To: cdt-dev@xxxxxxxxxxx
> > Subject: [cdt-dev] JNI support
> >
> > I am considering adding support for JNI programming.  The 
> > initial goals 
> > would be to provide awareness of javah, association of classes with 
> > native methods and the associated C/C++ implementation and command 
> > completion of JVM functions through the env pointer.
> >
> > I'm seeking advice.  Has any work been done in this direction?  Would 
> > this be considered for CDT or better as an independent plugin?  Would 
> > anyone (other than me) find this useful?
> >    
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>