sorry if this is OT, not sure if it is since it is a C++ q, sort of :).
I am working on a C++ library where all the files use the 8.3 convention. I
am now adding some collection classes. The typical library convention for
naming files is something like:
header ==> sfxmem.h
source ==> memory.cpp
where multiple memory classes are thrown into.
if the source spans multiple files, it is something like:
header ==> sfxfiles.h
source ==> files1.cpp, files2.cpp, etc.
obviously for my collection classes I would follow this convention with:
header ==> sfxcoll.h
but I am having a difficult time (yes I am obsessive compulsive) coming up
with what I think is a normal looking .cpp name.
these are some examples I have come up with:
collect.cpp
collect1.cpp
collect2.cpp
coll1.cpp
coll2.cpp
coll.cpp
colls.cpp
collectn.cpp
this last one seems kind of too cryptic... the other filenames have names
like apihook.cpp, menu.cpp, split.cpp, toolhelp.cpp, ie. none of the other
source files use something cryptic like that. and coll/colls... you look at
that, you have no dang clue what it is.
So I am kind of leaning towards "collect.cp p" right now, but that kind of
bothers me since it sounds like its collecting something rather then
collections of something.
any other ideas?
I am working on a C++ library where all the files use the 8.3 convention. I
am now adding some collection classes. The typical library convention for
naming files is something like:
header ==> sfxmem.h
source ==> memory.cpp
where multiple memory classes are thrown into.
if the source spans multiple files, it is something like:
header ==> sfxfiles.h
source ==> files1.cpp, files2.cpp, etc.
obviously for my collection classes I would follow this convention with:
header ==> sfxcoll.h
but I am having a difficult time (yes I am obsessive compulsive) coming up
with what I think is a normal looking .cpp name.
these are some examples I have come up with:
collect.cpp
collect1.cpp
collect2.cpp
coll1.cpp
coll2.cpp
coll.cpp
colls.cpp
collectn.cpp
this last one seems kind of too cryptic... the other filenames have names
like apihook.cpp, menu.cpp, split.cpp, toolhelp.cpp, ie. none of the other
source files use something cryptic like that. and coll/colls... you look at
that, you have no dang clue what it is.
So I am kind of leaning towards "collect.cp p" right now, but that kind of
bothers me since it sounds like its collecting something rather then
collections of something.
any other ideas?
Comment