Richard Dale Richard_Dale at
Sun Jun 3 19:59:26 UTC 2001

> > The main reason I added the Java api was in order to implement the Java
> > debugger part. At the moment the java debugger is started via KProcess, and
> > commands are piped to it in the style of jbb's gdb debugger front end. But
> > there are technical problems with setting breakpoints with that approach (very
> > difficult with nested classes, apparently unusable with anonymous classes). And
> > there are so many static final constant values inherited by a QApplication that
> > it overloaded the pipe connection. The debugger needs to use the JDI interface
> > - I had thought that was coming with JDK 1.3, but it has been back ported to
> > JDK 1.2 on my PPC Blackdown version - so I think it makes sense to use it now.

On Sun, 03 Jun 2001, Bernd Gehrmann wrote:
> Makes sense. I think the situation will be similar for anyone wanting to
> write a debugger for Python or Perl. Both have some debugging abilities,
> but they are hidden somewhere in the language itself and need some non-
> trivial interfaces. 
Yes, you mentioned using jpython for a debugger interface, and I thought
about it. It seems to me that there are two sorts of interface; one for
scripting, and one for plugins. I don't think it is possible to do a debugger
with just a scripting type interface (like jpython) - you need to be able to
instantiate widgets and so on for the UI, interact with signals for setting

BTW - what does the new ctags stuff do? I thought you had ported the
ctags parser to use the KDevelop class store - but I can't find any code to do
that. I'm keen on KDevelop Ruby support, and I see this in ctagsdlg.cpp:

static CTagsKindMapping kindMappingRuby[] = {
    { 'c', I18N_NOOP("class")               },
    { 'f', I18N_NOOP("function")            },
    { 'm', I18N_NOOP("mixin")               },
    { 0  , 0                                }

What is it all about, if that isn't a silly question?

-- Richard

to unsubscribe from this list send an email to kdevelop-devel-request at with the following body:
unsubscribe »your-email-address«

More information about the KDevelop-devel mailing list