Hello Matthias,
Having given further thought to r1404 and your recent comments I think
that we need to revert to the wlscope former interface to utilize this
new mechanism to its fullest. Example follows and here's the kernel
patch: http://pastebin.com/aSWRMU3V
Regards, Enoch.
\ wlscope, "wordli
Hi Enoch,
> Good, did svn update deciding conflicts in your favor :-)
;)
> Regarding the behind the scenes cleanup, do you allow merging of
> XT_HEADER into XT_DOCREATE ?
No. HEADER is useful for other things too.
I think more of something like
CREATE -> SCOPE -> HEADER -> .
something complet
Enoch writes:
> Matthias Trute writes:
>> I just applied your patch with my modification for the
>> the stack effect of the scope word. My second remark
>> would not change that (user visible) interface so I think
>> we can now play with the idea and can clean up the
>> code behind the scenes wi
Matthias Trute writes:
> I just applied your patch with my modification for the
> the stack effect of the scope word. My second remark
> would not change that (user visible) interface so I think
> we can now play with the idea and can clean up the
> code behind the scenes with less pressure ;)
He
Hi Enoch,
I just applied your patch with my modification for the
the stack effect of the scope word. My second remark
would not change that (user visible) interface so I think
we can now play with the idea and can clean up the
code behind the scenes with less pressure ;)
Matthias
---
Hello Matthias,
Matthias Trute writes:
> Hi Enoch,
>
>> > Only one remark so far.
>
> And now my second one. Its more a vague
> idea, not a streamlined chain of reason including
> a smart solution. Sorry.
>
> It is related to the way, the
> newly created word list entry is linked into it.
> HE
Hi Enoch,
> > Only one remark so far.
And now my second one. Its more a vague
idea, not a streamlined chain of reason including
a smart solution. Sorry.
It is related to the way, the
newly created word list entry is linked into it.
HEADER gets the WID for which the new word
is created. The sam
Matthias Trute writes:
> Hi Enoch,
>
> Only one remark so far.
>
> You defined the scope stack effect as ( addr len -- addr len wid )
> Usually forth follows the conecpt, that a word consumes its parameters
> to generate the new data. I'd prefer to keep this idea as the general
> design pattern.
Hi Enoch,
Only one remark so far.
You defined the scope stack effect as ( addr len -- addr len wid )
Usually forth follows the conecpt, that a word consumes its parameters
to generate the new data. I'd prefer to keep this idea as the general
design pattern. That changes scope to the stack effect
Matthias Trute writes:
> Hi Enoch,
>
> looks fine
>
> GIve me some more days to think about it (Im currently
> busy with other things) I find the sequence "(create) !e"
> sligthly strange. Your smudge change from an simple
> XT to WID-XT makes sense.
>
> Matthias
Hello Matthias,
I look forwa
Hi Enoch,
looks fine
GIve me some more days to think about it (Im currently
busy with other things) I find the sequence "(create) !e"
sligthly strange. Your smudge change from an simple
XT to WID-XT makes sense.
Matthias
> Hello Matthias & All:
>
> wlscope, "wordlist scope", is a deferred w
Hello Matthias & All:
wlscope, "wordlist scope", is a deferred word which enables AmForth appl
to choose the wordlist for a new voc entry based on its name. For
example, put all created words whose name begins with a tilde (~) on a
private wordlist. The default action is get-current.
Please find
12 matches
Mail list logo
