Array access and paths

I think this is the single most annoying thing about REBOL. Dealing with matrices etc is a nightmare!! I think there are a few problems with paths. At first, they look like a replacement for array indexing in other languages, but the fact that they only support a limited way of getting values is a big annoyance. Here is an example: list: [A 0 B 5 C 0 D 0] Say I want to change the number 5 following the B to 6. It's easy to read this number:

== 5 Or more generally:

== B

== 5 So far it looks very good. But then, try changing this value!

does not work.

Not very nice. Another example: I want to get a function from an array:

== [func [x][]]

** Script Error: 1 is missing its x argument ** Near: f: :func-array/1 Gisle

I don't think so. Have a look at REBOLek's rebsite %matrix.r script... realy nice and fast vector graphics example using matrices!

'at needs as a second parameter index not word... you can try this: change at list index? next find list 'b 6 or poke list index? next find list 'b 6 but I'd prefer your solution above...

try: probe pick :func-array 1 or probe first :func-array have fun, Cyphre

...

Another land mine not to step on if you take that last approach is this: the type of the value in IDX actually makes a difference in what the / means. If, as in your example, IDX is set to a word, then list/:idx is (almost) equivalent to select list idx but if IDX is set to an integer, then list/:idx is equivalent to pick list idx instead. (This also means that using integers as "symbolic keys" is problematic -- a pain in the neck.) I said "(almost) equivalent" above because of this situation

== E

** Script Error: Invalid path value: E ** Where: halt-view ** Near: list/:idx

== none in which throwing an error and returning NONE are *not* IMHO equivalent behavior. -jn-