Using org.eclipse.jdt.debug.eval / IEvaluationEngine? [message #250601] |
Fri, 11 January 2008 13:41 |
Eclipse User |
|
|
|
Originally posted by: mark_z.charter.net
I'm looking to do some work on an Eclipse plug-in, and need to be able to
filter through incoming events. While providing GUI options is probably
the typical way of doing this, such approaches are almost always quite
limiting. (For example, the Eclipse "Filters" for Problems/Tasks allows
for "contains" or "doesn't contain" conditions on the description.
However, what if I was to check for "starts with", or just wanted to use a
regular expression?)
I think how this is handled with Java breakpoints is awesome! Set a line
breakpoint, go to the breakpoint properties, enable condition, and then
the condition can be specified as Java - using any of the Java methods and
variables available to the line being debugged, as well as any features
natively provided by Java, e.g. use of regular expressions. (This seems
to be handled by
" org.eclipse.jdt.debug/model/org.eclipse.jdt.internal.debug.c ore.breakpoints.JavaLineBreakpoint.class ").
While most of the above code is all marked "internal", it seems to make
use of a public API available at
"org.eclipse.jdt.debug/eval/org.eclipse.jdt.debug.eval", including
"IEvaluationEngine" and "IAstEvaluationEngine" (and supporting classes).
***
My question is: are there any guides or examples to using this, beyond the
JavaDocs? Is anyone else using this at this time besides the Eclipse
internals?
For example, there are two evaluate(...) methods available on
IEvaluationEngine, one that takes an IJavaStackFrame, another that takes
both an IJavaObject and an IJavaThread. What is the best way of creating
or obtaining references to these objects?
--
Mark A. Ziesemer
http://www.ziesemer.com
http://blogger.ziesemer.com
|
|
|
Powered by
FUDForum. Page generated in 0.03757 seconds