Path: nntp.eternal-september.org!news.eternal-september.org!eternal-september.org!feeder3.eternal-september.org!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: dxf <dxforth@gmail.com>
Newsgroups: comp.lang.forth
Subject: Re: Parsing timestamps?
Date: Tue, 1 Jul 2025 14:00:18 +1000
Organization: i2pn2 (i2pn.org)
Message-ID: <b297e7f1a7839f4eeaf7491032144d153bda897e@i2pn2.org>
References: <1f433fabcb4d053d16cbc098dedc6c370608ac01@i2pn2.org>
 <a004d0f4acf945e054db77d86a4544fc@www.novabbs.com>
 <nnd$0d7645ea$11a210a3@2cd6ffa4d9a3008a>
 <4a4c38c99d22d97314ed5750af38430d@www.novabbs.com>
 <765bd244e1368b5691f18c748102470e8de1a30d@i2pn2.org>
 <nnd$0deda869$2559e613@c251414cde7edbe7> <103ilab$225q0$1@paganini.bofh.team>
 <cda70ea80eb98069a3060f95503d0853@www.novabbs.com>
 <2025Jun29.171314@mips.complang.tuwien.ac.at>
 <96f3b6d94af924cf1468a2cced37966d@www.novabbs.com>
 <d5ff6c298dff84dabc278ac1a28087d55126645e@i2pn2.org>
 <0cd5e9d5959101c1efa68a2d6d630e23@www.novabbs.com>
 <069f09501a3c6fcade18fdf83925d835514b42cc@i2pn2.org>
 <44b5f13fd49d8ddbd572ae583379d124@www.novabbs.com>
 <21113c70c36a86f0fd4c74c8d11d0947528ba70f@i2pn2.org>
 <20baae7dd561db60967a5937d2b59d9a@www.novabbs.com>
 <0db20ddf954106bbca40d9e83630033f108b9a8e@i2pn2.org>
 <a51bdcba2042924341742ebd69596f09@www.novabbs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 1 Jul 2025 04:00:22 -0000 (UTC)
Injection-Info: i2pn2.org;
	logging-data="2821114"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="XPw7UV90Iy7EOhY4YuUXhpdoEf5Vz7K+BsxA/Cx8bVc";
User-Agent: Mozilla Thunderbird
In-Reply-To: <a51bdcba2042924341742ebd69596f09@www.novabbs.com>
Content-Language: en-GB
X-Spam-Checker-Version: SpamAssassin 4.0.0

On 30/06/2025 10:40 pm, LIT wrote:
>>> The stack ops THEMSELVES may be, in a way,
>>> "canonical" — but not solving "each and every"
>>> programming task using them "no-matter-what", IMHO.
>>
>> But such would indicate a deficiency in Forth.  Do C programmers reach a
>> point at which they can't go forward?
> 
> You may want to raise your question on comp.lang.c

I can't imagine them answering in the affirmative.  C didn't introduce a
competing syntax thereby creating schism among its users.