Hi Alberto,

Many thanks for your prompt reply.

Our migration concerns only the OS from x86 bit to x64bit. Regarding the 
applications used like Xerces c++, these are going to remain in 32bit format. 
So, I would like to ask if Xerces c++ 3.1.2 32-bit application is able to run 
(compatible) on x64bit OS environment?

And another point please; Do you have any remarks that we should pay attention 
(mostly when building the source code) when changing version from Xerces 2.8 to 
3.1.2 32bit?

Thanks once again.

Best,
Matina

-----Original Message-----
From: EXT Alberto Massari [mailto:albertomass...@tiscali.it] 
Sent: Thursday, September 24, 2015 3:45 PM
To: c-users@xerces.apache.org
Subject: Re: Xerces C++ version

Hi Matina,

Il 24/09/15 13:58, Lakka, Matina (Nokia - GR/Athens) ha scritto:
> Hello,
>
> I am a Nokia engineer and I would like to ask you some questions regarding  
> Xerces C++. Our current version is 2.8 in our NetM product. We are planning 
> to migrate our product in windows server 2012 x64bit.
> My questions regarding Xerces C++ are:
> 1.  Is version 2.8 compatible with windows64bit?.

Yes, but read the next point

> 2.  If not, do you believe that we should move to Xerces C++ 3.1.2 for 
> compatibility issues?

Generally speaking, Xerces 2.8 is very old and hasn't been updated since 
Xerces 3 was released (2008). Furthermore, when completing the 64-bit 
support, we couldn't change a few APIs in order not to break the 
compatibility (i.e. XMLString v.2.8 uses the 32-bit 'int' and 'unsigned 
int' to reference sections of the string or its length, while v.3 uses 
the 64-bit size_t type), so if you plan to use huge values, Xerces 3.1.2 
is what you should use.
> 3. If yes, your latest version is open source or licenced?

Xerces is released under the open source Apache license ( 
http://www.apache.org/licenses/LICENSE-2.0)

Alberto

>
> Many thanks in advance.
>
> Best regards,
> Matina
>
>
> Matina Lakka
> MBB OMP MP R&D 22
> NOKIA
> Promitheos Str. 12, 145 64 Nea Kifissia
> Athens - Greece
> mail to: matina.la...@nsn.com
>
>
>
>

Reply via email to