RE: [cdt-dev] Patch to create ICoreModel interface

[Douglas Schaefer <dschaefe@xxxxxxxxxx>]

Actually John C and I were talking about this in relation to the DOM as 
well. As he mentions in 82873, which tool chain you are using also 
determines which language you are using, since we treat GNU C and C++ as 
"different" from other C and C++'s, mainly because they are...

I'm hoping the architectural changes to support additional languages is 
minimal since we already support two, kinda. The work for 82873 could be 
done independently and eventually feed into the logic used to select which 
language description to use. For now I was just planning on using the 
existing file type utilities as we do in the DOM, which currently always 
selects GNU C or C++, BTW.

Doug Schaefer
Ottawa Lab, IBM Rational Software Division



"Treggiari, Leo" <leo.treggiari@xxxxxxxxx> 
Sent by: cdt-dev-bounces@xxxxxxxxxxx
04/20/2005 10:39 AM
Please respond to
"CDT General developers list."


To
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
cc

Subject
RE: [cdt-dev] Patch to create ICoreModel interface






Sounds cool!  If we are going to start considering architectural changes
for supporting multiple languages, is it time to consider the concepts
of CDT-wide tool-chain definitions and CDT-wide build configurations?
See bugzilla #82873 for some previous, brief, discussions on this topic.

Regards,
Leo

-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Douglas Schaefer
Sent: Wednesday, April 20, 2005 9:45 AM
To: CDT General developers list.
Subject: Re: [cdt-dev] Patch to create ICoreModel interface

After fielding questions from a couple of people about Ada support in
the 
CDT. I've started to give this a bit more thought.

I guess the ideal situation is to minimize the amount of code necessary 
when adding support for a new language to the CDT. I've seen this
strategy 
used by a number of companies now in a number of places (unfortunately 
none of them on eclipse.org). I would think that having a whole new UI 
(perspective, editor, etc) for each language is too heavy weight, 
especially when you consider mixed language projects.

My current thought is to build on the mechanisms we have in place for
file 
types and add a language description interface that would be implemented

for a language (and probably a language UI interface for customizing 
certain UI elements like icons). We already have a number of places
where 
we check whether we are C or C++ to customize behavior in the CDT. The 
idea would be to make it extensible so that we can look up in a generic 
way to do the same tricks.

This may be a pipe dream but I've always been interested in Ada and have

started experimenting with these ideas, Maybe this will also help 
kickstart those who are interested in Ada (which includes AdaCore - the 
GNAT people https://bugs.eclipse.org/bugs/show_bug.cgi?id=91800) to help

contribute to this. I will also need help understanding what the Fortran

folk would need, including the Photran guys.

Doug Schaefer
Ottawa Lab, IBM Rational Software Division



Craig Rasmussen <crasmussen@xxxxxxxx> 
Sent by: cdt-dev-bounces@xxxxxxxxxxx
04/15/2005 11:22 AM
Please respond to
"CDT General developers list."


To
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>
cc
Nathan C ERDC-ITL-MS Contractor Prewitt 
<Nathan.C.Prewitt@xxxxxxxxxxxxxxxxxxx>, Greg Watson <gwatson@xxxxxxxx>, 
Alain Magloire <alain@xxxxxxx>
Subject
Re: [cdt-dev] Patch to create ICoreModel interface







On Apr 12, 2005, at 6:05 PM, Alain Magloire wrote:

> I am assuming that FDT, will have a perspective, a fortran editor
> and some other extra views.

Yes.

> For post cdt-3.0, maybe the goal should be to find the common core 
> denominators
> and refactor them out.  For the UI, it will be more tricky and we 
> should be
> ready to accept a lot clone/duplication for the first iterations.
>

I'm experimenting with this now.  When I have something I think is 
useful, I'll get
back to everyone.  I think I've learned enough to make progress.

Cheers,
Craig

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev