Re: Rationale for aligning data on even bytes in a Unix shell file?

On 30.04.2025 12:25, David Brown wrote:

On 30/04/2025 11:06, Muttley@DastardlyHQ.org wrote:

>
I've seen on more than one occasion C++ (not C yet) projects where there
were 2 files only different in case, eg: Network.cpp and network.cpp
where
the former would be the class and the latter would be procedural
support code.

 
I'd question the wisdom of such a convention.  I'd rather have clearer
separation of the filenames, or perhaps use different directories,
aiming to make it hard to mix up the names.  But maybe it is an
appropriate choice in some situations - perhaps alternative naming
schemes were considered worse in other ways.

I recall similar situations in our C++ contexts where name suffixes
were used (like "_util", "_aux", or similar) to disambiguate them.

I don't think it's a good idea to use the same names and resolve
them by organizing them through different directories only. I recall
we had used regularly -I compiler flags and I don't want to imagine
the hassle with same file names located in different directories.

Janis