From: Enoch <ix...@ho...> - 2013-03-30 07:57:10
|
Enoch <ix...@ho...> writes: > Matthias Trute <mt...@we...> 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 ;) > > Hello Matthias, > > 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 ? > > Regards, Enoch. Hello again, Below is an advanced example for (the revised) "wlscope" use. It shows how to encapsulate a large library of words. Note that since the following code allows multiple scope installs we can and perhaps should make "current-scope" invisible. Any comments? Regards, Enoch. ---------------------------------------------------------------------- wordlist constant can_list get-order can_list rot rot 1+ set-order : scope ( c-addr len -- wid ) 2dup 4 > if \ name length check s" can_" tuck icompare if \ name prefix check 2drop can_list exit then else drop then [ ' wlscope defer@ ] literal execute \ scope nesting safe ; ' scope is wlscope |