Re: single-xt approach in the standard

In article <vcfevo$6m9q$1@dont-email.me>,
Gerry Jackson  <do-not-use@swldwa.uk> wrote:
<SNIP>

Some of these, particularly the reporting has been suggested before but,
as you pointed out elsewhere everybody is an unpaid volunteer and nobody
has found the time or motivation to undertake such extensions. Are you
volunteering? I've just requested that the Forth 200X committee find
someone else to take over my test suite - so feel free to volunteer.
>
One thing not included in the Test Suite in the standard, as far as I
can see,  and not mentioned in your wish list is that the Hayes tester
assumes so much of the system is working before the tests actually start
- how do you test the tester? I thought about this and developed a
preliminary test based on the assumption that for automated testing at
least the interpreter must work. So it starts by using SOURCE TYPE (
comments ) and CR to output messages and include a commentary of how the
tests progress. If the displays are correct it tests >IN manipulation
and uses it as an interpretive IF to actually detect errors. Then it
goes on to do a basic test of the words used in the Hayes tester and so
on. This is included in the link above.

Practically speaking. ciforth went from a working fig-forth 16 bits i86
to a working 386 to a working ISO Forth to  linux 32 and 64 i86
and linux 32 and 64 arm , to a linux 64 risc-V.
What you describe is worthwhile, but not needed in most cases.
A c-based compiler like gforth will most likely work essentially
on the first try.

(Appreciate your work on extending the tests.)

>
--
Gerry
>

--
Temu exploits Christians: (Disclaimer, only 10 apostles)
Last Supper Acrylic Suncatcher - 15Cm Round Stained Glass- Style Wall
Art For Home, Office And Garden Decor - Perfect For Windows, Bars,
And Gifts For Friends Family And Colleagues.