Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Muttley@DastardlyHQ.org
Newsgroups: comp.lang.c
Subject: Re: Rationale for aligning data on even bytes in a Unix shell file?
Date: Wed, 30 Apr 2025 12:38:53 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 29
Message-ID: <vut5kt$9ne7$1@dont-email.me>
References: <vuih43$2agfa$1@dont-email.me>
 <vun04h$2fjrn$2@raubtier-asyl.eternal-september.org>
 <vun1nh$22hc5$3@dont-email.me>
 <vunak2$2p980$1@raubtier-asyl.eternal-september.org>
 <vunbgo$2q5u8$1@dont-email.me>
 <vunbjg$2q72n$1@raubtier-asyl.eternal-september.org>
 <vunhtp$301lb$1@dont-email.me>
 <vunib4$308ou$1@raubtier-asyl.eternal-september.org>
 <vunilp$30n57$1@raubtier-asyl.eternal-september.org>
 <vcMPP.1383459$f81.136711@fx48.iad>
 <vuobu5$3o38b$2@raubtier-asyl.eternal-september.org>
 <SxOPP.2986762$t84d.1636746@fx11.iad> <20250428203634.00006e09@yahoo.com>
 <vupvph$1a961$1@dont-email.me> <vurvru$34gfq$4@dont-email.me>
 <vusiqn$3ov7j$1@dont-email.me> <vuskeh$3p7jv$1@dont-email.me>
 <vusp6a$3ulkn$1@dont-email.me>
 <vustqu$2ga6$2@dont-email.me>
Injection-Date: Wed, 30 Apr 2025 14:38:53 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="4c8a2d891048b877383a09d39e1152c0";
	logging-data="318919"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+VzYJZCAEA0pzsu2CUUPb2"
Cancel-Lock: sha1:qehTrjHo7mIYn+VbPSBCChkyLRs=
Bytes: 3078

On Wed, 30 Apr 2025 12:25:34 +0200
David Brown <david.brown@hesbynett.no> wibbled:
>On 30/04/2025 11:06, Muttley@DastardlyHQ.org wrote:
>> On Wed, 30 Apr 2025 09:45:20 +0200
>> David Brown <david.brown@hesbynett.no> wibbled:
>>> More relevant to this group, it make also be convenient for people
>>> trying to work with big C code bases that were written on Windows and
>>> you now want to compile (for whatever target you want) them on Linux.
>>> I've seen code bases developed on Windows machines where the
>>> capitalisation of include directives was inconsistent - that works on
>>> case-insensitive filesystems, but not on case-sensitive systems.  (Yes,
>>> I know there are many other ways to deal with such issues, but putting
>>> the source code in a case-insensitive directory on ext4 is one option.)
>> 
>> 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.

Its certainly not a scheme I'd use, but I've also seen Makefile and makefile
in the same package build directory in the past.