- changed status to open
- removed comment
suggested naming convention for Cactus thorn files
urrently the user guide (http://einsteintoolkit.org/documentation/UsersGuide/UsersGuidech9.html#x13-144000C1.9.7) suggests prefixing file names with the thorn name, ie.
MyThorn_Functions.c
I was wondering what the rationale behind this is. There is no chance of conflicts during the build since each thorn is build in a subdirectory of its own. The extra prefix makes all filenames longer without adding anything to the functionality it seems to me.
In order to shorten the filenames and unclutter directory listings I would like remove the recommendation from the user guide.
Pull request is at: https://bitbucket.org/cactuscode/cactus/pull-request/8/suggested-naming-convention-for-cactus/diff
Keyword:
Comments (4)
-
reporter -
- removed comment
I agree. The wording could/should maybe add Fortran module names. These all end up in the common scratch directory, and without proper module naming people can get into trouble.
-
reporter - changed status to resolved
- removed comment
Applied in git hash 7744e3541d2d3664a030fea8713a8f647c051546 of the flesh.
-
reporter - edited description
- changed status to closed
- Log in to comment
Ian H