They are ideas for possible future implmentation.
See comments interspersed:
> Interesting comments Anton, however, I can't see how any of this
> could work...
>
> data/:(n: 150 'n)
>
> Here you have a Get-Paren. What's a Get-Paren? Parens are
> automatically evaluated....
That's right. The paren is evaluated first, and the result
could be combined with the colon to become a get-word.
Or that's the idea, anyway. Perhaps a get-paren! datatype
would need to be created to support that idea, and maybe not.
> data/(index + 2)
>
> The equivelant to that would be...
>
> pick data index + 2
>
> since index wasn't given a value then it would throw an error.
In this, my next idea, it gets the value from "context" or block
specified by that level of the path. A more complex example:
data: [sub [felafel 16 flatbread 1 ... ]]
data/sub/(felafel + 4)
which would access the 20th element of data/sub.
I repeat, they are just ideas. Obviously they
don't work now, but all the good stuff we are
getting now started off just as ideas too.
Note that I haven't thought of any really good uses
for the above ideas yet, but they may occur to me
later.
Anton.
> ~~Ammon ;~>
--
To unsubscribe from the list, just send an email to rebol-request
at rebol.com with unsubscribe as the subject.
