Jonathon,
I am not sure. If this is being sent out as Crosswire buisiness then the
Logo Chris designed is great for letter head. Troy, I am sure, has the
answer to that question. Otherwise we should come up with something that
looks professional. I vote for Chris to design it ;)
In Christ,
David
I don't like a sword at all. The Sword Revelation is taking about is a Word
that can divide between soul and spirit, between bone and marrow. The Sword
and the red Cross is a reminder of when the church became militant under
Constantine; an apostate church. It's a reminder of the Crusades where th
Boy, do I ever agree with Jorge.
At 01:57 PM 2/27/2002 -0600, you wrote:
>Hi,
>
>I actually like the downward pointing sword. It makes me think about
>two things: first of the double-edged sword of the Spirit, and also
>reminds me of the cross, due to its shape.
>
>I would not change anything i
Hi,
I actually like the downward pointing sword. It makes me think about
two things: first of the double-edged sword of the Spirit, and also
reminds me of the cross, due to its shape.
I would not change anything in it, but if you do, keep in mind the two
points above, as for me they are what ma
Hey Everyone,
As I see that I will be sending letters out to copyright holders
really, really soon. I am putting together the last little bit of
touches to the whole process that includes having a professional looking
letterhead, which means I need a logo for The SWORD Project (you know i
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
