Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Several questions considering the development of CDT based IDE

I have several questions considering the development of CDT based IDE
for a proprietary language:

1) According to the CDT 4 Extension Point Reference
the org.eclipse.cdt.core.language defines extension point to declare
language or language variants for C/C++ languages only. But the
Reference also states that completely different languages cannot be
modeled reasonably using this extension point. Is it reasonable to
expect that the language with the following properties will be
extended through this extension point? Of course the intention is to
CDT 5, 6.
Several details considering the language:
•	High-Level constructs are C like.
•	Function calls are C like.
•	Operators set is a subset of C99 operators.
•	Supports in language compilation directives.
•	Supports miscellaneous preprocessor commands.
•	50% keywords are just like in C. Another 50% of keywords are its own ones.

2) Lately we intend to incorporate debugger that will provide
different views and windows unavailable in the CDT debugger views.
org.eclipse.cdt.debug.core.CDebugger extension point looks to be very
restrictive. The ideal situation, from our point of view, is to use
CDT debugger as extendable platform adding/overriding its debuggers’
features/views. Is it possible? Two other options I can think about
are: 1) to add our debugger to the CDT source code tree or 2) to add
directly to the Eclipse workbench. Any thoughts are welcomed.

3) We also intend to add an analyzer tool to our IDE. I think that
building upon the CDT is out of question and the only way is to extend
Eclipse, isn’t it?

4) I couldn’t find any extension point for creating new perspective
inside the CDT Extension Point Reference. Does it mean that Eclipse
extension should be used instead?


Back to the top