On 2017-07-31 16:29, Ed Leafe wrote:
On Jul 31, 2017, at 12:12 PM,
[email protected] wrote:
So a static set of data, then? Like USPS zip codes?
Well, not exactly. It could be anything that only makes sense as a
complete set. Like parameters to a function, or small data
collections. Assume that in your app you pass around simple user
information, and this information contains username, role, and an
expiration date. So a logged-in user would be represented internally
as a 3-tuple of (username, role, expires). You could receive user
tuples from another part of the system, and know that there will be
those 3 elements in that order. That’s a pretty weak example, but it
would show the difference between a tuple and a list/array: it
wouldn’t make sense to have something like:
user_info.append(“green”)
to add an additional element, because we’ve defined a user as those 3
values. Likewise, deleting an item wouldn’t make sense, because now
you would not have the information that your app would need.
Ok. So an object collection of sorts, like the user properties you
described. Thanks.
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
