On Monday, September 12, 2022 at 2:03:53 AM UTC+10, Howerd wrote:
> On Tuesday, September 6, 2022 at 11:49:59 AM UTC+2, Wayne morellini wrote:
> > Thank you.
> Hi Wayne,
Thanks for this Howerd.
..
So, there is no attempt to port it to other processor families.
> > What about common services and feature code which could work on all editions of Colorforth?
> colorForth cf2022 is work in progress, and I do not intend to make anything backwards compatible with earlier versions, or compatible with other distributions such as the excellent GreenArrays ArrayForth.
Sorry, I meant going forwards across all new processor families, but there only seems to be
X86. I meant a common interfaces, storage and gui source code packages people could use to
run it stand alone, or under a. OS, so that all programs only need to be write once, unless you
want to customise. Sort of modem os concepts, as Linux does, and C only very remotely
attempted at its heart. That was the interest in Aha, as Jeff did significant work on what is
likely an optimised system.
> > What about a standard based on Colorforth
> You could use the current (latest) cf2022 as the current standard if you like, but it is likely to change. When I say "likely" I mean almost certainly.
Updatable standard anyway. I meant like formal source code and implementation standard,
even through a standards body like Ansi. A personal Forth, that requires no compatibility with
existing Ansi Professional Forth.
> The relationship between the F18 core (used in the GA144) and colorForth is complex. The F18 uses 5 bit opcodes that map to the F18 hardware, and these opcodes are compiled by the GreenArrays' ArrayForth, which is a version of colorForth running on a PC. It would be possible to re-write colorForth to use only the F18 opcode instruction set as an extra layer between the hardware and higher level colorForth code. This would make is run faster on an F18 core, but less fast on a PC. There is no point in doing this until there is some F18 (i.e. GA144) hardware available that has some sort of GUI available - I think that this would then deserve a new name - how about "machineForth:F18" ?
> colorForth runs on a PC at the moment - that is at least one thing that all colorForths have in common, including Pablo Reda's R4 (
https://github.com/phreda4/r4).
I would be talking about source code compatibility, like in Linux, which could be recompiled to
any new processor target using their instruction set.
I was mainly interested in how Chuck changed how forth instructions worked from colorforth to x18?
> Cheers,
> Howerd
Thanks again
Wayne.