Re: [Boost-users] [multi_index] SIGABRTinmulti_index_containerconstructor

From: JOAQUIN LOPEZ MU?Z (joaquin_at_[hidden])
Date: 2007-02-25 08:42:49

----- Mensaje original -----
De: Manuel Jung <gzahl_at_[hidden]>
Fecha: Domingo, Febrero 25, 2007 2:14 pm
Asunto: Re: [Boost-users] [multi_index] SIGABRT in
multi_index_container constructor
Para: boost-users_at_[hidden]

> "JOAQUIN LOPEZ MU?Z" wrote:
[...]
> > Can you (I mean, are you allowed to) provide a sketch of
> > the class where the offending queue class is being used?
> > I remember you said it's a member of a more complex class,
> > or something like that.
> 
> Hm, i think i can do that, nobody could use a part of the code 
> anyway (or would like.); But which part of it do you like?
> The Header? Or a part of the header? Or parts of code where
> the first error with the scripts are raising?

I don't really know :) I'm trying to gain more info on the
context where the core happens. Let's begin with say the
header and then we will pull from this thread if necessary,
OK?

> Greetings,
> Manu
> 
> Ps.: I have some question about the mem_fun. You cannot have a 
> index which is automaticly recalculated within a member
> function, can you? Im thinking about a function checking, if a
> try_mutex is locked. But i think, this is against the natured
> of a index. Am i right?

I'm not getting your question. Could you please reformulate
it using some pseudocode of your intended mode of usage? Thank
you!

Joaquín M López Muñoz
Telefónica, Investigación y Desarrollo