search

dasmithii / Kit

project manager for c/c++
MIT License
65 stars 6 forks source link

Differentiate between C and C++ modules #11

Closed dasmithii closed 10 years ago

dasmithii commented 10 years ago

C++ projects may link with C modules, but the contrary is not true, so there should be something to prevent accidental inclusions of C++ sources when only C sources are permitted.

Module name collisions are another issue.

emanuelpalm commented 10 years ago

I guess you need a file in each module/project which identifies it as either a C or C++ module.

Also, if each module stated the C standards relied upon, that would be very useful. If trying to import a module with POSIX.1-2008 requirement into a POSIX.1d project should result in a warning or error, just as importing a C++ module into a C project should.

As long as all modules have to reside in your CSV, collisions ought not to be a problem. You could include a quick look-up when running kit init (and some other calls) to check if there already is a module with the same name.