Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: candycanearter07 <candycanearter07@candycanearter07.nomail.afraid>
Newsgroups: comp.lang.c
Subject: Re: Which code style do you prefer the most?
Date: Fri, 28 Feb 2025 17:30:03 -0000 (UTC)
Organization: the-candyden-of-code
Lines: 33
Message-ID: <slrnvs3skl.1guhq.candycanearter07@candydeb.host.invalid>
References: <vpkmq0$21php$1@dont-email.me> <vplhc7$26ur1$3@dont-email.me>
 <87v7swzzl7.fsf@onesoftnet.eu.org> <vpn4qi$2j0hq$1@dont-email.me>
 <vpo20n$2o9ks$1@dont-email.me> <vpo7ec$2ovro$1@dont-email.me>
 <87a5a7k0ko.fsf@onesoftnet.eu.org> <vpprv6$34o4m$2@dont-email.me>
 <vpq3nm$35inm$4@dont-email.me>
 <slrnvs28aj.oo9l.candycanearter07@candydeb.host.invalid>
 <20250227202627.215@kylheku.com> <vprv73$3jah9$3@dont-email.me>
Injection-Date: Fri, 28 Feb 2025 18:30:03 +0100 (CET)
Injection-Info: dont-email.me; posting-host="7dde9cffca39a6aa8a3825e03fee7554";
	logging-data="3963829"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19Ies4AL5OL38MQ5N0gOyUSlmhaf15qQJdUH6erhUTmCQ=="
User-Agent: slrn/1.0.3 (Linux)
Cancel-Lock: sha1:SfrvusEClbRsxF80z8uc6u/Pp1g=
X-Face: b{dPmN&%4|lEo,wUO\"KLEOu5N_br(N2Yuc5/qcR5i>9-!^e\.Tw9?/m0}/~:UOM:Zf]%
 b+ V4R8q|QiU/R8\|G\WpC`-s?=)\fbtNc&=/a3a)r7xbRI]Vl)r<%PTriJ3pGpl_/B6!8pe\btzx
 `~R! r3.0#lHRE+^Gro0[cjsban'vZ#j7,?I/tHk{s=TFJ:H?~=]`O*~3ZX`qik`b:.gVIc-[$t/e
 ZrQsWJ >|l^I_[pbsIqwoz.WGA]<D
Bytes: 2896

David Brown <david.brown@hesbynett.no> wrote at 09:21 this Friday (GMT):
> On 28/02/2025 05:29, Kaz Kylheku wrote:
>> On 2025-02-28, candycanearter07 <candycanearter07@candycanearter07.nomail.afraid> wrote:
>>> David Brown <david.brown@hesbynett.no> wrote at 16:26 this Thursday (GMT):
>>>>> lines, /that/ would be a bug.
>>>>>
>>>> The bug, of course, is using Windows and Windows-style paths :-)
>>>>
>>> What's worse, its a WONTFIX!
>> 
>> Not sure what you're talking about. All Microsoft operating systems
>> going back to MS-DOS have accepted the forward slash as an alternative
>> path separator.  C:/Windows/System32 is a legitimate Windows-style path.
>
> Yes, you can often use forward slashes for directory separations in 
> Windows - but you can't do so everywhere.  There's no doubt that forward 
> slashes are the standard in the Windows world.

And, it's obviously the default for most paths.

>> Some incorrectly-written user space programs might not like it.
>> 
>
> Indeed - and that can be a pain.
>
> However, you can certainly use forward slashes in things like #include 
> directives when using gcc on Windows, or in makefiles - and that covers 
> a lot of my needs for path names!


Probably because gcc isn't made by MS.
-- 
user <candycane> is generated from /dev/urandom