realbasic-nug
[Top] [All Lists]

Re: Efficient Lisbox RowTag Implementation

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Efficient Lisbox RowTag Implementation
From: Charles Yeomans <charles at declareSub dot com>
Date: Sat, 31 May 2008 12:16:58 -0400
Authentication-results: mx.google.com; spf=pass (google.com: domain of realbasic-nug-bounces at lists dot realsoftware dot com designates 66.116.103.65 as permitted sender) smtp dot mail=realbasic-nug-bounces at lists dot realsoftware dot com
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <1F5D7379-4B88-4ABE-81F8-064A4F575B16 at verizon dot net> <8A496A12-32A3-4ED2-A2F1-3935F458F075 at declareSub dot com> <D95498D6-1AA7-44E7-9052-CA787F990D8D at verizon dot net>
On May 31, 2008, at 11:07 AM, Karen wrote:

>
> On May 31, 2008, at 10:57 AM, Charles Yeomans wrote:
>
>>
>> This would be a good place to use Pair objects.
>>
>>
>
> How would that be any different from my original solution of creating
> a class with only two variant properties?
>
> Objects of any sort ( instances of framework or our own classes) have
> more memory overhead than arrays, no?

Not necessarily.  I don't know how arrays are actually implemented,  
but given that they are reference-counted things with methods and  
properties, my guess is that they have a similar amount of memory  
overhead.  My suggestion would be to write the interface you want,  
then provide a simple implementation that works.  Now you have a  
baseline against which to measure your performance anxiety.  The Pair  
class is already written, so why not use it?

Charles Yeomans
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>