"I’m not sure how that would work since .S has no idea what you think
should be on the stack at any given time. It can only show you what is
there now."
It doesn't know, but it doesn't need to
... The stack has a fixed starting point. An underflowed stack's pointer
has gone beyond that point, so t
at .S leave the stack contents there so if you
> want to run another such test you would want to clear the stack first.
>
>
>
> Jeff Birt
>
>
>
> *From:* M100 *On Behalf Of *Alex ...
> *Sent:* Monday, March 29, 2021 1:25 PM
> *To:* m...@bitchin100.com
> *Sub
...@bitchin100.com
Subject: Re: [M100] Does anyone actually use MFORTH?
Cool, so newbie mistakes and ignorance. As long as my computer's working
properly. :)
What threw me off is in the book, (pg.25) it talks about returning usually 0
and printing STACK EMPTY, which is definitely not ho
it was the stack contents would be after it was
done. This was a great benefit to seeing what was happening.
Jeff Birt
From: M100 On Behalf Of John R. Hogerhuis
Sent: Tuesday, March 30, 2021 2:54 AM
To: m...@bitchin100.com
Subject: Re: [M100] Does anyone actually use MFORTH?
On Mon, Mar 29, 2021 at 11:25 AM Alex ... wrote:
> Cool, so newbie mistakes and ignorance. As long as my computer's working
> properly. :)
>
> What threw me off is in the book, (pg.25) it talks about returning usually
> 0 and printing STACK EMPTY, which is definitely not how the machine behaved
>
.@gmail.com
>Datum : 2021-03-29 - 23:08 (CEST)
>Till : m100@lists.bitchin100.com
>Ämne : Re: [M100] Does anyone actually use MFORTH?
>
>On 3/29/21 11:24 AM, Alex ... wrote:
>>
>> About the editor: I skipped over the whole chapter on the arcane line
>> editor and page/blo
"8)
A the memories.
I used Forth heavily in the 80's, mostly being a FigForth person, on Z80
systems.
What you describe is probably the single thing that killed Forth, the
fundamental incompatibilities between versions. Some did simple stack
checks before doing something silly, link the one
On 3/29/21 11:24 AM, Alex ... wrote:
About the editor: I skipped over the whole chapter on the arcane line
editor and page/block-based disk storage since this machine has none
of that. Using TEXT with .DO files works ok, as long as whatever I'm
doing doesn't trample the files in RAM.
Make
Cool, so newbie mistakes and ignorance. As long as my computer's working
properly. :)
What threw me off is in the book, (pg.25) it talks about returning usually
0 and printing STACK EMPTY, which is definitely not how the machine behaved
when trying it.
I don't expect everything to have bounds che
This is the default behavior for most all vintage 8-bit Forth implementations.
To do a bounds check might take 6-10 machine cycles for every word. This does
not seem like a lot, but it would have a noticeable impact on performance.
When I ventured Forth a few years ago I found that Forth Inc
On Sun, Mar 28, 2021 at 7:38 PM Alex ... wrote:
> Hello Tandy laptop nerds,
>
> So I've been reading Leo Brodie's "Starting Forth" and using my '102 as a
> playground / labrat. There's been a few inconsistencies I expected and can
> live with/work around, but I've noticed what seems like really b
12 matches
Mail list logo
