Haven’t worked with them yet, but my understanding is that a collection is an ordered list of values of possibly varying types. In 4D arrays, all of the values must be the same type. In a 4D collection, you can use mixed types as the elements.
Example: $MyCollection[0]:=“Hello” $MyCollection[1]:=5 $MyCollection[2]:=$AnObject $MyCollection[3]:=$AnArray $MyCollection[4]:=True ---------- Jeff Grann SuccessWare, Inc. > On Mar 15, 2018, at 10:43 PM, Keith Goebel via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Hi all. > 4D seem to be really fired up about the new Collection object available in > upcoming versions. > I’ve read the examples given in the blurb, but I have yet to read anything > that would give me an idea as to why I would want to use a Collection instead > of an Object. > It seems as though Collections are objects that don’t need a name parameter > to identify the content; but if I have to name a Collection, what’s the > difference between that and an Object item? > > There must be a very good reason for them, and I am sure I’m missing the > point, but what is it?... > Cheers, Keith ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
