Caroline,

That's good to know the background to that include file, I didn't know
about it. I'll definitely keep it in mind. I don't think the change I
made should affect you, let me know if it does.

Thanks

--------------------
Brady Johnson
Lead Software Developer - HydraSCA
Rogue Wave Software - [EMAIL PROTECTED]


-----Original Message-----
From: Caroline Maynard [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 13, 2007 6:29 AM
To: [EMAIL PROTECTED]
Subject: [Fwd: Re: [jira] Created: (TUSCANY-1529) Tuscany SDO native for
windows is not msvc backwards compatible]





-------- Original Message --------
Subject: Re: [jira] Created: (TUSCANY-1529) Tuscany SDO native for 
windows is   not msvc backwards compatible
Date: Mon, 13 Aug 2007 10:57:44 +0100
From: Caroline Maynard <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Newsgroups: gmane.comp.apache.webservices.tuscany.devel
References: <[EMAIL PROTECTED]>

Brady Johnson (JIRA) wrote:
> Tuscany SDO native for windows is not msvc backwards compatible
> ----------------------------------------------------------------

Don't I know it. In the PHP project the automated build servers for Win
use VC6, so we are obliged to use that compiler in the SDO for PHP
project. Since the Tuscany team decided to support only VC8, I usually
find some minor problems porting the code over - you'll find a trail of
these in the issues database where I've sent the fixes back as patches.
It's not really a big problem, more an inconvenience. However it was a
policy decision by the Tuscany committers at the time. YMMV.

Again, with the localtime behaviour, this came from concerns about using
non-reentrant versions of localtime(). You may not have noticed the
SDOUserMacros.h file - this mechanism was introduced so that consumers
of Tuscany C++ could adapt the macros to their environment. You can see
the PHP version here:

http://cvs.php.net/viewvc.cgi/pecl/sdo/commonj/sdo/SDOUserMacros.h?view=
markup

It would be helpful if you would keep this mechanism in place.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to