[REBOL] Re: UHURU unit structure
From: agem:crosswinds at: 30-May-2001 16:05
(list-kickoff again.. thanks for escribe :)
>->->->
From: Gabriele Santilli
Date: Wed, 30 May 2001 05:40:30
Volker Nitsch wrote:
> the trick here is to change the script.
> This can be done automatic, as long as the
> human knows how it works.
Exactly my point. I'm just suggesting to let BIND do the change
for you. :-)
> With my contexter you would write
[...]
It looks nice; I'm sorry I din't have the time to check it yet...
> note 'copy in a 'parse is like a 'set, easily overlooked..
> but not in usual code..
Yup, I was going to suggest making ALL words (excepts a given
list) local, but then it would be quite uncomfortable.
Your idea of parsing the code might be a solution, but it is not
general enough. (You'd have to keep ALIAS in consideration, or
even worse MY-SET: :SET; also, I could be using a dialect where
SET means something totally different...)
<-<-<-<
we could make the object and check by living context, which
words are bound to global context?
Checking against a list of rebol inbuilds,
all words wich are not there are made automatic local?
Inbuilds are trappt while debugging with 'protect-system.
This gives of course no warranty, but as Larry Wall would say:
rebolers are a polite society, they could break contexts,
but they would try not to do so.
So with good analysing tools for help most scripts should be ok?
Currently we have
- parsing like %nonlocal.r / contexter, some other.
Contexter is extensible in principle, so if one knows he does
[MY-SET: :SET],, he could patch his copy to know that.
- running script and compare global context before/after
- maybe the method above?
>->->
Regards,
Gabriele.
--
Gabriele Santilli <[giesse--writeme--com]> - Amigan - REBOL programmer
Amiga Group Italia sez. L'Aquila -- http://www.amyresource.it/AGI/
<-<-<-<
-Volker
