Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: Python recompile
Date: Mon, 03 Mar 2025 10:29:28 -0800
Organization: A noiseless patient Spider
Lines: 57
Message-ID: <864j0avugn.fsf@linuxsc.com>
References: <vq1qas$j22$1@gallifrey.nk.ca> <vq1uvb$qbuq$1@dont-email.me> <vq22nc$rvb8$1@dont-email.me> <vq24kd$rg6i$1@dont-email.me> <Tx1xP.2042$Oq27.1147@fx06.iad>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Date: Mon, 03 Mar 2025 19:29:33 +0100 (CET)
Injection-Info: dont-email.me; posting-host="6e9dfb039af0c0bf4d4ce41d1363f2d2";
	logging-data="1514301"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19Qz3GV1DRX178gT9rTj16ytyJAF+x8VrA="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:RC5LTyTBK4THvMFvnfWuXvmZBss=
	sha1:Yloc6W7R49n91SQpQwFglJWkcTk=
Bytes: 3808

scott@slp53.sl.home (Scott Lurndal) writes:

> James Kuyper <jameskuyper@alumni.caltech.edu> writes:
>
>> On Sun, 02 Mar 2025 16:58:20 +0000, Muttley wrote:
>>
>>> On Sun, 2 Mar 2025 15:54:19 -0000 (UTC)
>>> Lew Pitcher <lew.pitcher@digitalfreehold.ca> gabbled:
>>>
>>>> First off, this isn't really on-topic for comp.lang.c, as it is a question
>>>> regarding a linker, interacting
>>>> with the results of various options given to a specific compiler.
>>>
>>> Is there a comp.lang.c.linker group?
>>
>> comp.lang.c is about using the C programming language.  Linkers are
>> independent of the programming language, and can be used to link
>> together programs written in many different languages.  The subject line
>> and the text of the error messages indicate that it's a Python program,
>> so why would a group devoted to C be in any way appropriate?
>
> Frankly, I'd rather read about issues in the linker here than the
> interminable useless arguments about the precision and accuracy of
> fmod, which belong elsewhere (such as email), or pointless musings
> about the halting problem.

Personally I think questions and answers about the development
toolchain used in connection with C are okay in comp.lang.c.  I
share Scott's reaction to comments regarding fmod(), but I don't
think those postings should be excluded.  Postings about the
halting problem are of course way outside the envelope of what is
appropriate in comp.lang.c.

I count 25 messages in this thread.  Of those 25, one is the
original message asking the question;  two are replies pointing
out information that might be helpful to OP;  two are responses
to those replies, from OP;  one is Scott's reaction, the posting
I am responding to here.  (Incidentally I have benefited, in some
small measure, from the two first-level replies, and that benefit
has nothing to do with Python.)  If I haven't missed anything,
that leaves 19 postings that are about nothing but topicality.

By far a bigger problem with non-topical messages is when some
people who are regular participants in comp.lang.c, etc, keep on
talking about matters that are clearly outside the envelope of
what the newsgroup is expected to address, producing threads that
are dozens or sometimes hundreds of messages long.  What is even
more disappointing is that some of these same people sometimes
ding a message for being "off topic", even though they themselves
are far more guilty of the errant behavior.

My suggestion is, if anyone thinks a posting is "off topic", just
don't respond to it.  And don't make exceptions or excuses for
your own behavior.

My apologies for posting still another message that almost
exclusively about topicality.