Liste des Groupes | Revenir à cl c |
On 10/09/2024 12:55, David Brown wrote:There are probably Forth interpreters written in Forth that you could then run in your limited Forth in order to get any missing parts!On 10/09/2024 12:52, Bart wrote:Apparently:I've archived your post for if/when I get back to that project. (If I ever use Forth, it'll be on my own terms. I just tried it to see if it's still breathing:>
>
c:\qapps>qq forth
Bart-Forth
Type bye to stop
> 2 2 + .
4
> bye
>
But it handle :
>
: 2 1 ;
2 2 + .
>
and get the answer 2 ? :-)
c:\qapps>qq forth
Bart-Forth
Type bye to stop
> : 2 1 ;
> 2 2 + .
2
>
That's ram - the code was in an 8K ROM. And to be honest, the OS did not have a lot of features - the distinction between an OS and a BASIC environment was rather blurred for these kinds of home computers. (I'm sure you used a few of the home computers of that era, even if you were already a professional programmer at that time.)>An OS /and/ BASIC takes 125 bytes? You can't really complain about bloat here! Windows is probably 20GB and doesn't have Basic.So it looks like I already thought of it as my version.)>
>>>To give more background, bare ZX81 had 1kB RAM (including video RAM).>
You must mean /excluding/ surely? Otherwise there wouldn't be much left
from 1KB!
There is not much left. But there is a trick: boundary between
video memory and rest is movable, as you fill other part available
screen area shrinks. It does not take long time to have machine
completely filled out with no free space left (and IIRC some
small screen area for out of memory message)
So that meagre 1KB had to be shared?
>
Yes. 24 lines of 32 characters took 768 bytes, and the OS and BASIC took another 125 bytes. There was not a lot of space for user code and data!
Les messages affichés proviennent d'usenet.