Joachim,
Point well taken. I've rearranged things in SetKey to allow this
scenerio. Your test now works without segfaulting. Let me know if it
helps things in Bibletime.
-Troy.
Joachim Ansorg wrote:
>
> Troy,
> thank you for writing back!
>
> > target->SetKe
Thanks for the suggestion. We'll definitely consider it for 2.0
David White wrote:
>
> Why is it that containers have to "set" the key they are operating on?
> This seems a little awkward to me.
>
> I think it would be a good idea to move towards supporting full-strength
> bidirectional or ran
Troy,
thank you for writing back!
> target->SetKey((SWKey*)*target);
>
> The problem is that you are extracting a pointer to the SWKey of the
> current module (this is ok), then expecting it to remain valid long
> enough for a call to SetKey to complete, on the same module.
>
> Here's th
Why is it that containers have to "set" the key they are operating on?
This seems a little awkward to me.
I think it would be a good idea to move towards supporting full-strength
bidirectional or random-access iterators across modules, compliant with
the specifications of the C++ standard, so as
Joachim,
Did some hunting around and found a problem with your test program.
Not sure if it might be the same in Bibletime. Here's the scoop:
The offending line in your test program, below, is:
target->SetKey((SWKey*)*target);
The problem is that you are extracting a pointer to the SW
Troy,
Thank you for clearing this. I thought my mails are not read because nobody
understands my english or because I'm nerving people with the bugs I found.
Joachim
> Joachim,
> Don't feel like we don't write you back! Your posts usually require me
> to do some investigation and
Joachim,
Don't feel like we don't write you back! Your posts usually require me
to do some investigation and debugging. Know that I'm working on this
problem today.
-Troy.
Joachim Ansorg wrote:
>
> Yesterday I debugged strange crashes in BibleTime which were related to GBS.
