Re: [C++ SDO] Results from PHP testing
Edward Slattery [EMAIL PROTECTED] wrote on 10/07/2006 21:20:25: thankyou for that. The crash is something which we need to fix, and I will apply your change asap. I guess it probably wouldnt stop a release, but if we are re-spinning for any other reason I will make sure its in there. OK I think with the SDOString it was intended that we put in place a cast operator so that current users of the const char* would be unaffected. Would you consider directly casting the value to a (const char*) as an acceptable alternative? Yes, that would be fine. As things stand I have to invoke c_str(), which is not so neat. You are right, I forgot to update the release version number - and it should be updated with the SDOString stuff . Will update that at the same time. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[C++ SDO] Results from PHP testing
I tried building the M1 candidate in the PHP environment on Windows, with the following observations and issues: One backward-compatibility compilation problem: Type::SDOTypeNamespaceURI has been changed from a const char * to a const SDOString. This is easy enough to program round, but it seems unnecessary. Can this be reversed? One crash: See http://issues.apache.org/jira/browse/TUSCANY-529 One infrastructure comment: the runtime version is declared as 0.9.3, and has been for rather a long time. Shouldn't this be updated more regularly, in particular whenever API incompatibilities are introduced? This would make it easier to manage the code. Once I'd bypassed the two problems above, the PHP tests ran through OK, so it's looking promising. Now for some more platforms - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [C++ SDO] Results from PHP testing
thankyou for that. The crash is something which we need to fix, and I will apply your change asap. I guess it probably wouldnt stop a release, but if we are re-spinning for any other reason I will make sure its in there. I think with the SDOString it was intended that we put in place a cast operator so that current users of the const char* would be unaffected. Would you consider directly casting the value to a (const char*) as an acceptable alternative? You are right, I forgot to update the release version number - and it should be updated with the SDOString stuff . Will update that at the same time. cheers, Ed. On 10/07/06, Caroline Maynard [EMAIL PROTECTED] wrote: I tried building the M1 candidate in the PHP environment on Windows, with the following observations and issues: One backward-compatibility compilation problem: Type::SDOTypeNamespaceURI has been changed from a const char * to a const SDOString. This is easy enough to program round, but it seems unnecessary. Can this be reversed? One crash: See http://issues.apache.org/jira/browse/TUSCANY-529 One infrastructure comment: the runtime version is declared as 0.9.3, and has been for rather a long time. Shouldn't this be updated more regularly, in particular whenever API incompatibilities are introduced? This would make it easier to manage the code. Once I'd bypassed the two problems above, the PHP tests ran through OK, so it's looking promising. Now for some more platforms - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
