On 10/26/08 05:58, Takashi Ono wrote:
In the meantime, I have a slight concern as I do not know the detailed pros and cons about using stlport and most of all other platforms use stlport as defaults.
The stable URE ABI unfortunately exposes details that vary with the STL implementation being used. Therefore, platforms that (for historic reasons) started out using (a specific version of) STLport have to stick with that choice. New platforms are free to chose any STL implementation for which they can reasonably guarantee stability. Typically, they have a choice of using the compiler's native STL implementation or OOo's STLport. In such a case, the compiler's native STL implementation is probably the better choice, as it is likely to be easier to configure and more standards conforming.
I am not sure whether the mingw build is to be considered a new platform, or whether it should be kept compatible with OOo's existing Windows platform (wntmsci10/11/12, using the Microsoft compiler). (I assume the former, as I doubt that binaries built with mingw C++ are ABI-compatible with binaries built with the Microsoft C++ compiler.)
-Stephan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
