[cdt-dev] C vs C++ Projects

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] C vs C++ Projects

From: "Brad Jarvinen" <Brad.Jarvinen@xxxxxxxxxxxxxx>
Date: Fri, 13 Feb 2004 15:53:29 -0800
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <http://dev.eclipse.org/pipermail/cdt-dev/>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <http://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <http://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AcPyjJRnMJynTfrQQ9y5mh5Y5ZPbww==
Thread-topic: C vs C++ Projects

What is the major reasons for having C and C++ projects separated?  I currently have the cnature and ccnature in my projects I generate for both C and C++ projects and the content assist seems to use the extension of the file to determine whether the file is C or C++ for code templates.  

Is there a major reason I shouldn't use one project that includes both cnature and ccnature for both C and C++ projects rather than having separate C and C++ projects?

Thanks,
Brad

Follow-Ups:
- Re: [cdt-dev] C vs C++ Projects
  - From: Douglas Schaefer

Prev by Date: RE: [cdt-dev] Issues with unit tests for CDT 1.2.1 RC1
Next by Date: [cdt-dev] Fwd: Opening and reading less to build the CModel
Previous by thread: [cdt-dev] Problem in debugging
Next by thread: Re: [cdt-dev] C vs C++ Projects
Index(es):
- Date
- Thread

Breadcrumbs