Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Tue, May 28, 2002 at 01:00:09PM +0100, Angus Leeming wrote:
>> > Unrelated question: Why are there boost::shared_ptr<> al over the place?
>> > Sort of 'pimpl'?
>>
>> Where. I don't have the source to hand remember.
|
| /// The cache contains data of this type.
| typedef boost::shared_ptr<GCacheItem> CacheItemType;
>
| /** The cache contains one item per file, so use a map to find the
| * cache item quickly by filename.
| * Note that each cache item can have multiple views, potentially one
| * per inset that references the original file.
| */
| typedef std::map<string, CacheItemType> CacheType;
>
>
>> > Next question: Why is GCacheItem derived from SigC::Object? Shouldn't it
>> > rather have signals as members?
>>
>> Because the graphics converter emits a signal when the file is converted
>> to a loadable format. We want to know when to load it don't we?
>
| Ok. I probably just don't understand the significance of being an
| SigC::Object.
>
| Being an SigC::Object means I can receive signals? One or any number?
>
| [How does this relate to the boost signals (of which I read
| something _very_ recently...;-}]
boost::trackable is the equivalent of SigC::Object.
Have a look at the signals.patch that I posted some days ago.
--
Lgb
