|Who debugs the debuggers, part III
||[Apr. 27th, 2006|09:14 pm]
...See also Part II...
I suppose the Javadt approach ran out of steam. For some reason,
it now takes a horribly long
time to invoke the request on an
(A horribly long time is time enough to have a smoke, and then to come back, see it's still not done and go surf the web enough to leave the zone.)
So I decide to bite the bullet and look into creating an Eclipse plugin...
...which turns out to be not too hard. And, while I am at it, I will use
Java 6, and undo
the horrific crap I did to get around the lack of MethodExitEvent.returnValue()
However, here's little but symptomatic discovery (duh!).
Javadt does not like a
null EventSet -- it just does not
nulls (which is ok, I suppose, for a throwaway reference
implementation). So I was returning an empty
EventSet to it all
the while. But Eclipse will indiscriminately call
resume() on it,
which is not what I want. So I am back to returning
null. Fine. But how many of such little things would render this "framework" not really a framework... Or should this all be configurable?