item delimiter defaults
pete at lcsql.com
Fri Nov 22 05:33:20 CET 2013
I agree that arrays are better. Now if only LC would return an array of
data returned from a database query, main key record number, subkey column
name, we might not need this new column entity.
On Nov 21, 2013 3:15 PM, "Monte Goulding" <monte at sweattechnologies.com>
> On 22/11/2013, at 9:21 AM, Mark Wieder wrote:
> > If anything, I'd argue that things should be the other way around:
> > that there be *no* default itemDelimiter, and the use of items without
> > having explicitly defined the delimiter should result in a runtime
> > error.
> Ooo.... now that would break a heap of code... :-)
> I already avoid items like the plague they are. Array syntax can be much
> more descriptive:
> Look at this 6 months later and you know you're dealing with a name:
> set the text of field "company" to tArrayA[tIndex]["name"]
> Look at this 6 months later and you need to go and look at where your list
> is created to remember what was in item 3:
> set the text of field "company" to item 3 of line tIndex of tData
> Stuff like this makes my head spin:
> get item 3 of line tIndex of tData
> set the itemDelimiter to "|"
> get item 2 of it
> --- and so on...
> Then there's the never having to worry about delimiters being in your data
> M E R Goulding
> Software development services
> Bespoke application development for vertical markets
> mergExt - There's an external for that!
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the use-livecode