|
From: George R. <gr...@us...> - 2003-05-21 18:47:04
|
This is a known bug in ICU 2.4. Could you try ICU 2.6 d01 and see if it's
fixed? When the final release of 2.6 is available around June 13th, you
can use that release.
FYI you should be using the icu4c-support mailing list for these compiler
problems.
George Rhoten
IBM Globalization Center of Competency/ICU San Jose, CA, USA
"Daniel Suski" <SU...@de...>
Sent by: icu...@ww...
05/21/2003 06:35 AM
To: ic...@ww...
cc:
Subject: Compiler error with std::vector<UnicodeString>
Hi,
I'm using ICU2.4 with VS .NET and when I try to compile the following
code:
class UnicodeStringVector: public std::vector<UnicodeString>
{
....
}
I get the following compiler error:
C:/Program Files\_Development\Visual Studio .NET\Vc7\include\xmemory(42) :
error C2660: 'icu_2_4::UMemory::operator new'
: function does not take 2 parameters
C:/Program Files\_Development\Visual Studio
.NET\Vc7\include\xmemory(127) : see reference to function template i
nstantiation 'void std::_Construct(_T1 *,const icu_2_4::UnicodeString &)'
being compiled
with
[
_T1=icu_2_4::UnicodeString
]
C:/Program Files\_Development\Visual Studio
.NET\Vc7\include\xmemory(126) : while compiling class-template membe
r function 'void std::allocator<_Ty>::construct(std::allocator
<_Ty>::pointer,const icu_2_4::UnicodeString &)'
with
[
_Ty=icu_2_4::UnicodeString
]
C:/Program Files\_Development\Visual Studio
.NET\Vc7\include\vector(19) : see reference to class template instan
tiation 'std::allocator<_Ty>' being compiled
with
[
_Ty=icu_2_4::UnicodeString
]
C:/Program Files\_Development\Visual Studio
.NET\Vc7\include\vector(35) : see reference to class template instan
tiation 'std::_Vector_val<_Ty,_Alloc>' being compiled
with
[
_Ty=icu_2_4::UnicodeString,
_Alloc=std::allocator<icu_2_4::UnicodeString>
]
d:
\IBM\Development\BackingBuilds\saow\src\dni\com\umg\common\ccode\dniccio.hpp(115)
: see reference to class tem
plate instantiation 'std::vector<_Ty,_Ax>' being compiled
with
[
_Ty=icu_2_4::UnicodeString,
_Ax=std::allocator<icu_2_4::UnicodeString>
]
In xmemory.h the problem commes from the method void std::_Construct()
// TEMPLATE FUNCTION _Construct
template<class _T1, class _T2> inline
void _Construct(_T1 _FARQ *_Ptr, const _T2& _Val)
{
// construct object at _Ptr with value _Val
new ((void _FARQ *)_Ptr) _T1(_Val);
}
That "new" statement seems not to be handled correctly by the
icu_2_4::UMemory::operator new...
I'm sorry but this is rather urgent and we will need a fix for that if it
turns out to be a code problem in ICU 2.4...
Thanks very much for your help.
Best Regards / Mit freundlichen Grüßen,
Daniel Suski
-------------------------------------------------------------------
IBM Deutschland Entwicklung GmbH
S,S&S - Websphere Banking Solutions Development
su...@de...
_______________________________________________
icu mailing list
ic...@os...
http://oss.software.ibm.com/developerworks/oss/mailman/listinfo/icu
|