Hi,
> >> tstring: "password/jj"
> == "password/jj"
> >> tstring: to-path tstring
> == password/jj
There are many issues about this expression.
1)
p: to-path "a/b"
creates a path composed of a single item which is itself th path a/b.
You can verify this with this:
length? :p
first :p
type? first :p
length? first :p
2) if you the path composed by 2 words ("a" and "b") you must do:
first to-path "a/b"
or
first to-block "a/b"
or
load "a/b"
or
first load/all "a/b"
3) to-path (like to-block) does not bind words to the global context, so you
must bind it manually or let load make the work for you.
4) If you do not want to use load, you must bind manually a path you can do:
p: first bind to-block "a/b" 'system
5) last official beta releases have changed the mode in which path are
evaluated (check the changes doc)
---
Ciao
Romano
--
To unsubscribe from this list, just send an email to
[EMAIL PROTECTED] with unsubscribe as the subject.
