This is all I can get out of debugging...
Program received signal SIGSEGV, Segmentation fault.
0x7646ee73 in sword_SWKey___str__ (my_perl=, cv=)
at Sword.cxx:2360
2360return const_cast(self->getText());
Probably not helpful at all...
btw it's r2955.
On Mon,
I did not discovered any issue in Swete. Log of what been checked attached
(plus sign mean that chapter(s) verified).
2013/8/5 Chris Little
> Yes, if you have time to check Swete, that would be great. It's probably
> the most important one other than Rahlfs'.
>
> If you do check it, you can ski
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think we are relatively safe to assume that these are at least of
type long (or unsigned long) and at least 32 bits wide. I doubt Sword
will be ported to 16- or 8-bit architectures.
God bless!
Jaak
On 12.08.2013 12:44, Troy A. Griffitts wrote:
> So
Sorry, one more for gcc:
http://gcc.gnu.org/onlinedocs/cpp/If.html#If
On 08/12/2013 11:42 AM, Troy A. Griffitts wrote:
On 08/12/2013 10:46 AM, Jaak Ristioja wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2013 10:34, Troy A. Griffitts wrote:
OK, I've put together a scheme which
On 08/12/2013 10:46 AM, Jaak Ristioja wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2013 10:34, Troy A. Griffitts wrote:
OK, I've put together a scheme which moves the new version macros
into our swversion.h file. The new scheme goes out to 4 segments
as we support in the SWVer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.08.2013 10:34, Troy A. Griffitts wrote:
> OK, I've put together a scheme which moves the new version macros
> into our swversion.h file. The new scheme goes out to 4 segments
> as we support in the SWVersion class. Here are the defines.
> Pleas
For *Xiphos* developers: (reporting here due to the nature of the
observation)
I just added a ticket here:
https://sourceforge.net/apps/trac/gnomesword/report/1?asc=0&sort=ticket&USER=dfh4npp
Then I remembered that this didn't seem like what I had done on previous
occasions.
The other tracker i
OK, I've put together a scheme which moves the new version macros into
our swversion.h file. The new scheme goes out to 4 segments as we
support in the SWVersion class. Here are the defines. Please add your
comments and ask question, but I hope these will be self-explanitory.
My only concer
