Hi James, short answer: yes
bottom line: can't get&set with the same word see: this just came up again in the last week or so: look for the thread called "change/at" On Wed, 2 Oct 2002, James Marsden wrote: > Can anyone shed some light on this behaviour: > > n: 4 > bob: array/initial [8 8] 1 > ; this works fine > bob/:n/4: 2 > > ; this dies horribly > bob/4/:n: 2 > > It seems to let a variable be part of an assignment as long as it is not the > last entry in the path... > > Is this a bug or a design feature?? > > > James. > > > -- > To unsubscribe from this list, please send an email to > [EMAIL PROTECTED] with "unsubscribe" in the > subject, without the quotes. > -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
