[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [cdt-dev] Thought on "New C/C++ Project"
|
UPC users want "new UPC project" (they want to be more of a "first class
citizen" - their quote)
...Beth
Beth Tibbitts (859) 243-4981 (TL 545-4981)
High Productivity Tools / Parallel Tools http://eclipse.org/ptp
IBM T.J.Watson Research Center
Mailing Address: IBM Corp., 455 Park Place, Lexington, KY 40511
"Treggiari, Leo"
<leo.treggiari@in
tel.com> To
Sent by: "CDT General developers list."
cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
clipse.org cc
Subject
10/26/07 04:15 PM RE: [cdt-dev] Thought on "New C/C++
Project"
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
>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
Sent: Friday, October 26, 2007 12:03 PM
To: CDT General developers list.
Subject: [cdt-dev] Thought on "New C/C++ Project"
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 Ada (via
the Hibachi project) at some point too.
Feel free chime in any thoughts you have on this.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com.
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
