Hi Rich,
I've tried to look at things from the angle of prevention, rather than
cure. The IDE and all of our tools were built without the use of
debuggers. We prefer to use a set of assertion mechanisms to continually
test the integrity of the system while it is executing. We find with
this approach we just don't have a need for single stepping. I'm hoping
the require/ensure from Eiffel will make it into Java soon (yes, I've
seen both JContract and IContract - they haven't been updated for quite
a while).
I was just talking to a developer yesterday who described this
situation. He said he got into a catatonic state hitting the next, next,
next button when, if he had sat back and looked at the big picture, he
would have solved his problem faster.
That said, I am currently working on the debugger which will be included
in the next release. It is built on top of the Java2 JDI (early access
from Sun), so it won't work with 1.1 and I don't have a version for
Linux yet :( so I am SuFfErInG another OS...
I'm hoping the JDI will be available from Blackdown after the Java2
release?
Regards, Jon.
Elixir Technology Pte Ltd.
Rich Edwards wrote:
>
> Sounds interesting, but... does it include a debugger?
>
> IMHO, that's the only real requirement out of an IDE - everything else
> is just fluff.
>
> - Rich
>
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
