<p>You can convert a C project to a C++ project and vice versa. An example of
when this may be useful is if you create a C project, your requirements change during the course of
the development, and you
need to continue coding in C++. Since the initial project was coded in C,
the parser will not recognize certain semantics such as "class", or keywords
such as
"public", "private", and "template". You need to create a C++ project to
make the parser and other tools aware of the language change. You can simply
convert your C project to a C++ project rather than creating a new C++ project, copying your project files over and resolving source control issues.</p>
<h2>A few notes about projects</h2>
<ul>
<li>When you create a file within a project, a record (local
history) is created of every time that you modify the file and how you modify it.
For more information about local history, see <b>Workbench User Guide > Reference > User interface
information > Development environment > Local history</b>.</li>
<li>Spaces in projects and filenames can cause problems with some
tools, such as the make utility or the compiler.</li>
<li>Be careful when using case alone to between distinguish files and projects. UNIX-based
operating system
filenames are case-sensitive, but Windows filenames are not. Therefore, Hello.c and
hello.c overwrite each other in Windows, but are separate files in UNIX.</li>
</ul>
<p>For more information about projects, see <b>Workbench User Guide > Concepts > Workbench > Resources</b>.</p>
