In article <
f09cedd6937a47ef584fe642e15b5a8e@news.novabbs.com>,
mhx <
mhx@iae.nl> wrote:
none wrote:
In article <2023Dec3.144835@mips.complang.tuwien.ac.at>,
Anton Ertl <anton@mips.complang.tuwien.ac.at> wrote:
albert@cherry.(none) (albert) writes:
If Marcel Hendrix claims ANSI compliance, take it with a grain of
salt. For example in miscutil.frt hex prefix '$' is used with impunity.
Marcel Hendrix can't have claimed ANS compliance for miscutil.frt because >that file is not in the latest tForth source distribution (~1995).
So I presume this comment applies to the version you have on
your website.
You conveniently forget the conflict that arose in the 90's.
I was the librarian and I rejected your whole sale replacement
of the source. I continued with documenting each defect and
solving it, possibly analysing your source whether it was a solution
of the problem.
From that time one each change was documented with the
defect or wish list item it solved.
So I'm sorry but the latest source distribution is on my site and
it is much more recent. That was the version we supplied to
the one paying customer we had. I have been never relieved from
the librarian function.
It is GPL after all. You are perfectly legit to keep a fork
on your website.
The file is present in almost all releases of iForth, and Albert
van der Horst has the first LAST CHANGE entry:
---
* LAST CHANGE : 911002 AH Split into source and configuration parts
---
The change was done before the file was renamed miscutil.frt.
I was merely the first to record changes in the file header.
I vaguely recall that somebody took offense with an ANS Forth
compatibility phrase (before 2005, the oldest backup I can find).
Currently, the header reads
---
(*
* LANGUAGE : ANS Forth
* PROJECT : Forth Environments
* DESCRIPTION : Useful words
* CATEGORY : Configuration
* AUTHOR : Marcel Hendrix
* LAST CHANGE : 2020-09-06 15:35:06 hs; CIRCBUFFER sets first cell to 0
at runtime
* LAST CHANGE : 2019-02-08 07:17:21 hs; @CPUTICKS uses @cpuid as a
serializing instruction ...
---
iForth can (still) be made to warn for non ANS-2012 words.
You could add a caption in your documentation, to run this facility
for people who publish a program developed using iforth and
add it to the header of the file, assuming all other words are
ANSI.
-marcel
Groetjes Albert
--
Don't praise the day before the evening. One swallow doesn't make spring.
You must not say "hey" before you have crossed the bridge. Don't sell the
hide of the bear until you shot it. Better one bird in the hand than ten in
the air. First gain is a cat spinning. - the Wise from Antrim -
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)