Mailinglist Archive: zypp-devel (227 mails)

[Michael Andres <ma@xxxxxxx>]

On Tue, Apr 01, Josef Reidinger wrote:

> >   IMO return the matching sat::Solvables. All the other types (ResObject
> >   Package, PoolIterm, Selectable) can (or will) be constructed from the
> >   sat::Solvable as needed.
> Thanks for response.
> only one another think which I don't understand:
>   I look at code and and look like that way Solvable->PoolItem is harded 
> then back way. Because PoolItem store Resolvable and from resolvable is 
> easy extract solvable (code looks easy to execute). 

Yes, but this is subject to change. I'd like the poolItem to store the 
Solvable, and delay creation of the resobject. But' that's not (so ) 
urgent.


>                                                     But constructing 
> PoolItem from solvable needs finding throught whole pool (which can be 
> optimalize, but I think is much difficult then extract solvable from 
> resolvable).

The method used is called 'ResPool::find', but the pool knows where he 
created his item. So find is basically range check and array access.

   return( slv_r.id() < mystore.size() ? mystore[slv_r.id()] 
                                       : PoolItem() );

The PoolItem ctor from solvable is nothing but a convenience. Only the 
pool actually constructs them. 

-- 

cu,
    Michael Andres

+------------------------------------------------------------------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862  27AC 3FB8 9E3A 27C6 B0E4
+------------------------------------------------------------------+
Michael Andres             YaST Development            ma@xxxxxxxxxx
SUSE LINUX Products GmbH, GF:  Markus Rex,  HRB 16746 (AG Nuernberg)
Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0
+------------------------------------------------------------------+

-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx