I wouldn't be in favor of using {}. Problem is that LC currently accepts
those characters as delimiters for the keys of an array. I don't use them
on purpose but every now and again I notice I typed one by mistake. Seems
like a backwards compatibility problem.
Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
On Wed, Aug 20, 2014 at 8:23 AM, <j...@souslelogo.com> wrote:
> I was thinking :
> set the indexedarray of myArray to true
> set the indexedarray of myArray to false
>
> but then what happens when you switch that property from true
> to false for the same array within a handler ?
>
> Same question for "{}" notation : what happens when the same
> handler contains these 2 successive lines :
> add 1 to myArray{10}
> add 1 to myArray[10]
>
> Best
> jbv
>
> > How about using {} instead of []?
> >
> > Bob S
> >
> >
> > On Aug 20, 2014, at 07:24 , Richard Gaskin
> > <ambassa...@fourthworld.com<mailto:ambassa...@fourthworld.com>> wrote:
> >
> > So if we were to propose that LiveCode add indexed arrays, the first
> thing
> > we'll want to do is come up with the syntax for specifying those when
> > those are what we want, ideally allowing all other usage to continue
> using
> > associative arrays as they have all these years.
> >
> > Suggestions on what that syntax should look like?
> >
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
