| RE: [cdt-dev] Thought on "New C/C++ Project" |
|
>Anyway, it does bring up the issue of all these New C
Project, new C++ Project, new C# Project, etc. wizards. >Could we not make the language choice part of the
Toolchain. For example have a GCC C Toolchain and a GCC C++ Toolchain? Then we
could have a Mono C# Toolchain as well to >support C# development? Again, if
the toolchains were part of the CModel, we could use that to handle the C
versus C++ issues we have today and get rid of the ccnature finally. My personal, off the top of my head
opinion, would be to keep the current New C Project, New C++ Project, New C#
Project model. Leo From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer Hey gang, We’ve recently found a new-ish project on SourceForge
that is doing a C# plug-in. I’ve hooked up with one of their developers
and am taking a look at what they have. It looks like they’ve gone
through the duplication that new *DT’s tend to do. Despite the lack of
interest in the community and time I have to spend on it I still think C# on
CDT would work. I already have keyword highlighting and a build integration
done with pretty minimal work. Anyway, it does bring up the issue of all these New C
Project, new C++ Project, new C# Project, etc. wizards. Could we not make the language choice part of the Toolchain.
For example have a GCC C Toolchain and a GCC C++ Toolchain? Then we could have
a Mono C# Toolchain as well to support C# development? Again, if the toolchains
were part of the CModel, we could use that to handle the C versus C++ issues we
have today and get rid of the ccnature finally. I’m not sure that would work but it may be an idea.
But then that leaves us back what to call the new project wizard. New CDT
Project wouldn’t make sense all the time. We’d probably want to
integrate Fortran and Feel free chime in any thoughts you have on this. Doug Schaefer, QNX Software Systems |