I know this has always been called "CppUnit", but since
".cpp" is more-or-less deprecated and ".cc" is the
more-or-less universally preferred suffix for C++ files,
wouldn't it be nice if this were called "ccUnit" instead?
Presumably a less controversial request: could the file
extensions of the implementation files be changed to ".cc"?
In our build environment (into which ccUnit [sic] is being
integrated), ".cpp" means "C Pre Processor", and we have
make rules that deal with files with those suffixes. I
think that ".cpp" for "C Pre Processor" is a fairly
common usage.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I agree that cpp may cause conflicts. We use it on an alpha where the standard extension for C++ files is .cxx, and .cpp is already used for C preprocessor file. For our purpose it was sufficient to rename all files from .cpp to .cxx. By the way, what is the standard extension for C++ header files? We use .hxx. Is there a GNU standard for this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As your message points out, there really is no "Standard" extension for these files.
I'm claiming that current "best practice" is to call them .cc and .h. Of the other top contenders it appears that .C is falling out of favor, and .cxx's usage is only common for certain platforms.
As far as I can tell, .cpp isn't a top contender.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Changing the file extensions to .cc probably won't cause much grief. But I don't think I would rename the project. I found this project because I was reading about XProgramming and got interested in unit tests. In several articles they referenced Feather's CppUnit. I found this project by searching for CppUnit and I don't think much would be gained by breaking that tie.
Just my opinion.
Cory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmmn... evidently you're not using the (unfortunately) most influential compiler (M$VC). Yes, I do use gcc, but mainly M$VC. The whole cc/CC/cxx/cpp thing is just silly really.
Aside from the name change being of no real value, in the context of unit tests CPP is more likely, IMNSHO, to evoke C Plus Plus.
Whoever heard of a C PreProcessor unit test?
JMTCW
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I know this has always been called "CppUnit", but since
".cpp" is more-or-less deprecated and ".cc" is the
more-or-less universally preferred suffix for C++ files,
wouldn't it be nice if this were called "ccUnit" instead?
Presumably a less controversial request: could the file
extensions of the implementation files be changed to ".cc"?
In our build environment (into which ccUnit [sic] is being
integrated), ".cpp" means "C Pre Processor", and we have
make rules that deal with files with those suffixes. I
think that ".cpp" for "C Pre Processor" is a fairly
common usage.
Thanks!
I agree that cpp may cause conflicts. We use it on an alpha where the standard extension for C++ files is .cxx, and .cpp is already used for C preprocessor file. For our purpose it was sufficient to rename all files from .cpp to .cxx. By the way, what is the standard extension for C++ header files? We use .hxx. Is there a GNU standard for this?
As your message points out, there really is no "Standard" extension for these files.
I'm claiming that current "best practice" is to call them .cc and .h. Of the other top contenders it appears that .C is falling out of favor, and .cxx's usage is only common for certain platforms.
As far as I can tell, .cpp isn't a top contender.
Changing the file extensions to .cc probably won't cause much grief. But I don't think I would rename the project. I found this project because I was reading about XProgramming and got interested in unit tests. In several articles they referenced Feather's CppUnit. I found this project by searching for CppUnit and I don't think much would be gained by breaking that tie.
Just my opinion.
Cory
Hmmn... evidently you're not using the (unfortunately) most influential compiler (M$VC). Yes, I do use gcc, but mainly M$VC. The whole cc/CC/cxx/cpp thing is just silly really.
Aside from the name change being of no real value, in the context of unit tests CPP is more likely, IMNSHO, to evoke C Plus Plus.
Whoever heard of a C PreProcessor unit test?
JMTCW