Richard Dale Richard_Dale at tipitina.demon.co.uk
Wed Dec 13 13:34:54 UTC 2000

On Tue, 12 Dec 2000, John Birch wrote:
> > There are various ways to do this, but one would 
> > be to have two separate class browsers at the same time. Quite conceivable 
> > and there could be benefits from this approach. But it can't be done because 
> > the framework will not allow it. (note: I'm not suggesting we actually do 
> > this!)
On Tue, 12 Dec 2000, Bernd Gehrmann wrote:
> I assume you mean two parsers, not two class browsers? It's perfectly
> possible to have many class browsers [2]. If you want to support several
> languages in the same project, you have to rethink everything related
> to the sourceinfo anyway. You can't just let several different parsers
> put their stuff into the same class store, because you must be able
> to distinguish classes written in different languages (e.g. for the
> 'Add method' menu item). So you must have several class stores and
> you must be able to distinguish them. It's possible to extend the
> framework in this way. It's possible to extend other frameworks in
> this way. But you will never get support for that automagically
> in either of them.
I think different languages can put their stuff into the same class store if
you were to have special (ie hidden from the user) top level namespaces for each
language, eg '_java.', _objc.' and none for C++. With different class
stores, I would expect it might be harder to design the UI so that you can
browse different languages at the same time

-- Richard

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

More information about the KDevelop-devel mailing list