I am trying to use C++ exceptions with PPC2003 SDK and
get the following unresolved externals:
y.obj : error LNK2001: unresolved external symbol "const
type_info::`vftable'" (??_7type_info@@6B@)
y.obj : error LNK2001: unresolved external symbol "void
__stdcall `eh vector destructor iterator'(void *,unsigned
int,int,void (__thiscall*)(void *))" (??
_M@YGXPAXIHP6EX0@Z@Z)
y.obj : error LNK2019: unresolved external symbol "void
__stdcall `eh vector constructor iterator'(void
*,unsigned int,int,void (__thiscall*)(void *),void
(__thiscall*)(void *))" (??_L@YGXPAXIHP6EX0@Z1@Z)
referenced in function _DllMain
Here is the code that generated the error messages:
struct A {
A() {}
~A() {}
};
BOOL APIENTRY DllMain( HANDLE hModule, DWORD
ul_reason_for_call, LPVOID lpReserved )
{
try {
A a[2];
throw 1;
} catch(int) {}
return TRUE;
}
Does Microsoft support C++ exceptions with WinCE.NET 4.2
(it seems so from the product page)? Did anyone get it to
work successfully?
Thanks!
Oleg
--
Regards,
Maarten Struys
PTS Software bv
"Oleg Kibirev" <Oleg.K...@oracle.com> wrote in message
news:260701c3734b$c4216450$a601...@phx.gbl...
"Oleg Kibirev" <Oleg.K...@oracle.com> wrote in message
news:260701c3734b$c4216450$a601...@phx.gbl...
--
Michael Salamone
Entrek Software, Inc.
www.entrek.com
"Maarten Struys" <maarten...@nospam.pts.nl> wrote in message
news:ubgHJu2c...@tk2msftngp13.phx.gbl...
--
Regards,
Maarten Struys
PTS Software bv
"Michael J. Salamone" <mik...@entrek.com> wrote in message
news:enLqXd5c...@tk2msftngp13.phx.gbl...
Thanks.
Sanjay
"Udara W Gunawardane" <uda...@empriseit.com> wrote in message news:<ewerOE5c...@tk2msftngp13.phx.gbl>...
It seems that Microsoft released a broken PocketPC SDK - PPC2003 does
support both C++ exceptions and RTTI but the SDK compiler fails to produce
the virtual destructor for type_info, so RTTI won't work and thus typed C++
exceptions won't either.
One person has suggested defining:
type_info::~type_info() {}
somewhere in your application, as a temporary workaround, but it's not clear
whether that will cause other problems!
Another way around this is apparently to get hold of some files from
www.entek.com, which provide their own RTTI support library - again, it's a
temporary fix until the SDK compiler gets sorted.
Hope that helps,
Dr. James Weatherall