| [JEM][OT] Why not use org.eclipse.jdt.debug? [message #77627] |
Tue, 18 January 2005 01:21  |
Eclipse User |
|
|
|
Originally posted by: lmorley.wpi.edu
A few months ago, I posted a thread regarding creating a new JVM, and
Rich was very helpful in suggesting jem proxy remote. We've also been
trying to look at what's already available, and lately I've been taking
a look at org.eclipse.jdt.debug.eval and org.eclipse.jdt.debug.core (and
the whole JDT JDI stuff in general). At first glance something like
IAstEvaluationEngine would be helpful; say, for example, in taking a
string like "Integer.parseInt(myVar)" and getting a real value out of it
(which is a real scenario we'd have to deal with). I was hoping to take
advantage of the fact that you guys already went through the design, and
might have a few words about the choices you made. I apologize if this
might not be the exact place, or if this is a bit inappropriate.
(As for IAstEvaluationEngine, IJavaDebugTarget, et al, I hit a brick
wall, as it doesn't seem -- and reasonably so -- that you can create
variables at run-time in a debugged application. I'm still looking for a
solution.)
I'm very appreciative for anything you can tell me, it's been a learning
experience thusfar.
--
Liam Morley
Computer Science Undergraduate
Worcester Polytechnic Institute
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03643 seconds
Home