Path: ...!weretis.net!feeder9.news.weretis.net!i2pn.org!i2pn2.org!.POSTED!not-for-mail
From: mhx@iae.nl (mhx)
Newsgroups: comp.lang.forth
Subject: Re: portable or =?UTF-8?B?bm90PyBWb2xhdGlsZSBzdHJpbmdz?=
Date: Tue, 13 Aug 2024 18:44:49 +0000
Organization: novaBBS
Message-ID: <30e35d436c018c00a16f763d0c59ac34@www.novabbs.com>
References: <nnd$3d18fe02$76aace5d@9eae9618ab09b239> <v9cfp9$364en$1@dont-email.me> <nnd$05375ad3$6e018fac@ef3f66902c87c893>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Info: i2pn2.org;
	logging-data="2467227"; mail-complaints-to="usenet@i2pn2.org";
	posting-account="t0bSWFIQDvYvkkhDiPIIv6byulC6WbSEwXWMJpxc4k0";
User-Agent: Rocksolid Light
X-Rslight-Site: $2y$10$q25PEOZ1dFdTllV6.Oh.jOuHq./i5/3w5iAGjVTs9dtCCdfn0wXEy
X-Spam-Checker-Version: SpamAssassin 4.0.0
X-Rslight-Posting-User: 59549e76d0c3560fb37b97f0b9407a8c14054f24
Bytes: 1789
Lines: 19

On Mon, 12 Aug 2024 9:01:48 +0000, albert@spenarnc.xs4all.nl wrote:

>
> Okay let's say it out loud. Classic Forth is not fit for handling
> strings.

I don't agree. Classic Forth is perfectly fit for handling strings.
It just needs some user-defined words added. The longer such words
are not standardized, the better the final result will probably be.

> A denotation that generates a constant string "blablabla" that has
> a status as a number is long overdue.

Which illustrates my point. Having a built-in string type denoted
by quotes might be a good thing. It is hard to find a argument
against that when numbers are already a comparable exception that
nobody has found a way to get rid of. And maybe we can then even
tick strings and numbers like everything else?

-marcel