Path: ...!weretis.net!feeder9.news.weretis.net!news.quux.org!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: Python recompile
Date: Fri, 14 Mar 2025 10:37:32 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 21
Message-ID: <vr10tc$14r3v$1@dont-email.me>
References: <vq1qas$j22$1@gallifrey.nk.ca> <vq4om7$1dbo2$2@dont-email.me>
	<vq6dqh$1pskk$1@dont-email.me> <vq6f8p$1pmnk$1@dont-email.me>
	<vq6gqc$1qcp8$1@dont-email.me> <vq6ips$1pmnk$2@dont-email.me>
	<vq6j5h$1qosf$1@dont-email.me> <20250304092827.708@kylheku.com>
	<vq7g1p$1vmg5$1@dont-email.me> <vq94dt$2boso$1@dont-email.me>
	<vqcsk7$23bfo$1@paganini.bofh.team> <vqefn1$3flpt$1@dont-email.me>
	<vqeu5c$3imil$1@dont-email.me> <vqeun4$3iqbq$1@dont-email.me>
	<vqfcbe$3lkkc$1@dont-email.me> <871pv861ht.fsf@nosuchdomain.example.com>
	<20250308192940.00001351@yahoo.com> <vqi1ge$8jg8$1@dont-email.me>
	<vqibt3$ahu0$3@dont-email.me> <vqiibq$bq1o$7@dont-email.me>
	<20250309012626.00001276@yahoo.com> <vqiugc$dv5o$2@dont-email.me>
	<20250309112807.0000489d@yahoo.com> <vql2bf$uei7$2@dont-email.me>
	<20250310152000.00004955@yahoo.com> <vqmvei$1dhpg$1@dont-email.me>
	<vqnm4r$1i1s0$5@dont-email.me> <vqosj3$1spcv$1@dont-email.me>
	<vqq7q2$25gtn$4@dont-email.me> <vqrfk1$2gqoc$1@dont-email.me>
 <vr01ql$9jrt$1@dont-email.me>
Injection-Date: Fri, 14 Mar 2025 11:37:33 +0100 (CET)
Injection-Info: dont-email.me; posting-host="c64ad6ecd0132592859ece920a3cbfb4";
	logging-data="1207423"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18DtX5wB4KDMHIrbrBH0ZIS"
Cancel-Lock: sha1:JUOrACxjFdYy4vbmocX7E3iOTPM=
Bytes: 2635

On Fri, 14 Mar 2025 01:47:02 -0000 (UTC)
Lawrence D'Oliveiro <ldo@nz.invalid> wibbled:
>On Wed, 12 Mar 2025 08:11:45 -0000 (UTC), Muttley wrote:
>
>> On Tue, 11 Mar 2025 20:52:19 -0000 (UTC)
>> Lawrence D'Oliveiro <ldo@nz.invalid> wibbled:
>>
>>> How much are you going to pay?
>> 
>> Nothing, because who knows what libc will do if the descriptor exceeds
>> that soft limit.
>
>But you said “I'd bet money on the kernel/libc authors taking this into 
>account when allocating user space descriptor values”. But they didn’t -- 
>otherwise we *would* know what libc would do, and you yourself have 
>admitted that we don’t. Therefore you have lost the bet. QED.

You can't lose a bet if the race hasn't even started. Someone would need to exam
ine the
libc code and check. I have better things to do.