Troy,
In r2973, you added some handling for hi rend=ol.../hi in OSIS
documents being converted to plaintext that I would like to see
disappear quickly and forever on account of being all kinds of bad.
First, this is not valid OSIS. rend is not an attribute on any OSIS
element. Switching
The win32 utilities based on SWORD 1.7.0RC4 (r2979) are at the usual
location:
http://crosswire.org/ftpmirror/pub/sword/utils/win32/
--Chris
___
sword-devel mailing list: sword-devel@crosswire.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's not a compiler bug.
Basically the C++ standard does not enforce an initialization order
for globals. So the compiler is free to initialize such stuff in any
order. I think your toolchain just happens to be lucky enough to do
that in an the order
Jaak, I disagree that your comments have anything to do with this problem. I
have confirmed that the 3 file globals immediately preceding the problem global
have been initialized. I doubt you are saying the c++ standard doesn't support
initializing a global array and then initializing a global
On 11.09.2013 22:35, DM Smith wrote:
The C++ standard does specify order w/in a file (top down), but not
across files.
Yeah, something like that. It is explained in detail in 3.6.2 of the C++
03 standard. I've attached a patch which fixes the issue for these
globals (and as a side effect might
