Isn't that basically what I just said? I guess you just worded it more
eloquently than I;)
ck
-Original Message-
From: R. Bhakti Klein
i'm thinking it has something to do with the fact that in the first
example, you're modifying a variable, whereas in the second one, you're
yes i just explicated it more explicitly.
Colin Kettenacker wrote:
Isn't that basically what I just said? I guess you just worded it more
eloquently than I;)
ck
-Original Message-
From: R. Bhakti Klein
i'm thinking it has something to do with the fact that in the first
i'm thinking it has something to do with the fact that in the first
example, you're modifying a variable, whereas in the second one, you're
modifying the contents of a field cast member, which is treated
differently by lingo.
-bh
Colin Kettenacker wrote:
The direct access to the cast
for some reason, it seems to prefer the syntax
put "B" into txt.item[1].char[3]
instead of
txt.item[1].char[3] = "B"
but it will do what you want it to that way..
--bhakti
Andy Driscoll wrote:
Hello All,
OK, been doing the Lingo thing professionally for over 6 years now and
I'm
--- METHOD 1, PRODUCES ERROR
txt = "Andy*is*cool"
the itemDelimiter = "*"
put txt.item[1]
-- "Andy"
put txt.item[1].char[3]
-- "d"
txt.item[1].char[3] = "B" -- this produces the error, "Wrong Type"
Yeah it's a wierd one, yet it works if you modify your last line
At 5:55 PM -0600 2/21/01, Andy Driscoll wrote:
Hello All,
OK, been doing the Lingo thing professionally for over 6 years now and
I'm stumped...
(and thanks to John Sweeney for verifying that I'm NOT crazy and
suggesting I share this one...)
Same thing-- 2 different ways of doing it.
First
