Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Patch to create ICoreModel interface

On Apr 20, 2005, at 7:45 AM, Douglas Schaefer wrote:

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 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.

A facility to customize UI elements like icons would help a great deal.

On Apr 20, 2005, at 8:57 AM, Douglas Schaefer wrote:

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 am able to create mixed Fortran and C applications simply by creating a tool chain with both Fortran and C compilers. It seems to me that a "Managed Make C
Project" should really just be a "Managed Make Project", with a language
neutral icon.  We never think of Make as being language specific.

So mixed Fortran and C projects seems to work so far (except that my Fortran files have a pesky little .c icon). So I think a minimalist approach can take us
quite far.


Back to the top