Bugzilla from stephan.menzel@gmx.eu wrote:
Joaquin,
Am Donnerstag, 4. Dezember 2008 21:18:36 schrieb Joaquin M Lopez Munoz:
and everything compiles and works just fine. Your key for HostSetOrderedIndex is std::string, which is exactly what you want AFAICS.
...well, actually it's asio::ip::address but I get your point.
Oh yes, sorry, I locally replaced asio::ip::address with std::string to compile your code with minimal hassle.
to explicitly specify that you want your elements sorted according to lthost. Note that the fact that HostSetOrderedIndex uses lthost does not affect in any manner the way HostSetRandomIndex operates.
Ahhh, that is what you meant. I did specify lthost for the ordered index, but never for the random index. That's why the sort() went wrong. All right. It isn't possible to specify lthost for these operations in the RandomIndex parameters, is it?
It isn't possible, random_acces roughly mimics std::list, which does not allows for the specification of any sorting predicate at declaration time.
Anyway, just curious. One working version is just fine, especially since it's the more efficient one.
Great lib, that MultiIndex! I just love it, and well documented too.
Glad to know it's being useful to you. Best, Joaquín M López Muñoz Telefónica, Investigación y Desarrollo -- View this message in context: http://www.nabble.com/-multiindex--custom-key-extractor-problem-tp20839161p2... Sent from the Boost - Users mailing list archive at Nabble.com.