Hi Richard,
On 5 Mar 2007, at 16:22, Richard Gaskin wrote:
Dave wrote:
> Well he should have known better then!
First, Jeanne is a woman.
Just a typing error, didn't meant to imply otherwise.
No problem. Errors happen.
Yes and as long as they are addressed in a timely manner there is
Dave wrote:
> Well he should have known better then!
First, Jeanne is a woman.
Just a typing error, didn't meant to imply otherwise.
No problem. Errors happen.
Second, that a mistake is made in any product's documentation does not
necessarily mean the author doesn't understand the concept
Hi All,
This is the type of thing where threads tend to go south here:
>>> Whoever wrote the documentation didn't understand how Arrays in
>>> RunRev work.
>>
>> That would be hard to believe. Jeanne DeVoto, who wrote most of the
>> documentation, is one of the foremost documentation experts on
Dave wrote:
The documentation is unclear. It should read:
delete global myArray[17] -- removes the array element whose key is
"17".
note: the use of 17 here does not refer to a numeric index, but
rather to a key that is used to look up the element in the array. It
is possible to use the
Dave-
Friday, March 2, 2007, 12:21:35 AM, you wrote:
> Interestingly (perhaps!!) is that ActionScript 3 (don't know about
> earlier versions) treats associative arrays and objects as equivalent
> things. From their docs: "Associative arrays are unordered
> collections of key and value pairs. "
Hi,
Please see comment below regarding the documentation in RunRev.
All the Best
Dave
On 3/2/07, Dave <[EMAIL PROTECTED]> wrote:
Whoever wrote the
documentation didn't understand how Arrays in RunRev work. If they
had been called something less confusing then the problem would not
have aris
On 1 Mar 2007, at 19:02, J. Landman Gay wrote:
Dave wrote:
When I read the part quoted above in the documentation I thought
for a moment that myArray[17] was some special usage and wasted
times checking that it worked the way I thought it worked. There
is really no point in describing th
On 3/2/07, Dave <[EMAIL PROTECTED]> wrote:
Whoever wrote the
documentation didn't understand how Arrays in RunRev work. If they
had been called something less confusing then the problem would not
have arisen and I wouldn't have wasted time!
Having neither programmed in SNOBOL4 of SPTOBOL I h
On 2 Mar 2007, at 06:48, Mark Wieder wrote:
If I'm remembering this stuff correctly, the terms Hashtable and
Associative Array refer to the same thing. Which one you use depends
on how you were brought up. I suppose it may be simpler just to think
of them as unordered collections of key/value pa
Dave-
Thursday, March 1, 2007, 9:23:14 AM, you wrote:
> I agree this can be confusing. I haven't read the documentation
> recently, but I remember being caught out in the past when the docs
> implied that arrays could have "numerical" keys. I was under the
> impresson that deleting a key from s
I agree with the versatility of associative arrays, but the conventional
array uses different functions, like in Flash, so the following may help a
new user who has experience in other programming languages.
(Forget for today abut 0-based versus 1-based array addressing)
Flash
Deleting imgArr[17]
Dave wrote:
When I read the part quoted above in the documentation I thought for a
moment that myArray[17] was some special usage and wasted times checking
that it worked the way I thought it worked. There is really no point in
describing the RunRev type of Array in these terms since there is
Dave wrote:
On 1 Mar 2007, at 16:17, Richard Gaskin wrote:
Dave wrote:
delete global myArray[17]
does not delete the 17th element, unless the key "17" just happens
to the 17th element. The documentation is confusing on this
point. Also the whole name "Array" for this datatype is
confus
On 1 Mar 2007, at 16:17, Richard Gaskin wrote:
Dave wrote:
delete global myArray[17]
does not delete the 17th element, unless the key "17" just happens
to the 17th element. The documentation is confusing on this
point. Also the whole name "Array" for this datatype is
confusing, a bette
On 1 Mar 2007, at 15:16, Dave wrote:
Yes, that's what I thought, so:
delete global myArray[17]
does not delete the 17th element, unless the key "17" just happens
to the 17th element. The documentation is confusing on this point.
Also the whole name "Array" for this datatype is confusing
Dave wrote:
delete global myArray[17]
does not delete the 17th element, unless the key "17" just happens to
the 17th element. The documentation is confusing on this point. Also
the whole name "Array" for this datatype is confusing, a better name
would be "table", since it doesn't behave l
Yes, that's what I thought, so:
delete global myArray[17]
does not delete the 17th element, unless the key "17" just happens to
the 17th element. The documentation is confusing on this point. Also
the whole name "Array" for this datatype is confusing, a better name
would be "table", sinc
delete global myArray[17] -- removes 17th element of that array
Correct? Does it remove the 17th element, rather the element with
the Key that is "17" ?
It deletes the key that is named "17". Try the following to check:
on mouseUp
repeat with k = 1 to 20
put "abc" into tArray[k * 2
Dave,
arrays are tricky. To delete array variables I use
delete variable myArray[myKey]
Andre
On Mar 1, 2007, at 11:10 AM, Dave wrote:
Hi,
Please see text from the RunRev 2.8.x Dictionary copied below. Is
the line:
delete global myArray[17] -- removes 17th element of that array
Correc
Hi,
Please see text from the RunRev 2.8.x Dictionary copied below. Is the
line:
delete global myArray[17] -- removes 17th element of that array
Correct? Does it remove the 17th element, rather the element with the
Key that is "17" ?
Thanks a lot
All the Best
Dave
delete local tempVari
20 matches
Mail list logo
