Sujet : Re: portable or not? Volatile strings
De : dxforth (at) *nospam* gmail.com (dxf)
Groupes : comp.lang.forthDate : 14. Aug 2024, 03:09:12
Autres entêtes
Organisation : Ausics - https://newsgroups.ausics.net
Message-ID : <66bc11c8$1@news.ausics.net>
References : 1 2 3 4
User-Agent : Mozilla Thunderbird
On 14/08/2024 4:44 am, mhx wrote:
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?
'might be a good thing' - these would have to be the most used words
in Forth :)