Subject: | |
From: | |
Reply To: | |
Date: | Wed, 20 May 2009 18:33:31 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On 20/05/2009, at 17:10 , Stockly, Ed wrote:
> I should have been more clear:
>
>> Mark R>> List concatenation is more for combining two lists that
>> might
> already have multiple items each.
>
> I was referring to that statement when I said
>
>> Me> Yes, but if you're dealing with records and combining lists and
>> records
> this is bound to be problematic.
>
> And, I should have specified that using concatenation in combining
> lists and
> records that have multiple items is bound to be problematic.
>
>> set recordList to {}
>> set oneRecord to {foo:1, bar:"hello"}
>> set end of recordList to oneRecord
>> set twoRecord to {foo:2, bar:"Goodbye"}
>> set end of recordList to twoRecord
>> recordList
>> --->{{foo:1, bar:"hello"}, {foo:2, bar:"Goodbye"}}
>
> Yes. This is not concatenation and is exactly what Mark, Mark and I
> suggested.
>
> I think we have reached a consensus.
>
> ES
Ed,
you> > And, I should have specified that using concatenation in
combining lists and records that have multiple items is bound to be
problematic.
You can not concatenate lists and record because you might get a list
or a record (1 case that I can think of) and this is not what one
wants in general.
My first example indicated in how to concatenate a list with a list of
1 record.
Concatenating lists and records is problematic. End of story.
Deivy Petrescu
[log in to unmask]
|
|
|