.:: Bots United ::. - View Single Post

Pierre-Marie Baty · **Re: Metamod badf error, yet.... -** 19-12-2004

Yes, embedded linker directives in #pragma's are nice, however they don't allow the specification of undecorated names, that's why they have limited usefulness... For example, if this

Code:

#ifdef WIN32
#pragma comment(linker, "/EXPORT:GiveFnptrsToDll=_GiveFnptrsToDll@8,@1")
#pragma comment(linker, "/SECTION:.data,RW")
#endif

works for metamod plugins, it doesn't for hook DLLs. I believe MSVC doesn't decorate GiveFnptrsToDll the same way. And that sucks a bit. Anyway, it's not a MSVC-specific problem, any C++ compiler decorates function names to resolve overload ambiguities.

	(#10)
Pierre-Marie Baty Roi de France Status: Offline Posts: 5,049 Join Date: Nov 2003 Location: 46°43'60N 0°43'0W 0.187A	Re: Metamod badf error, yet.... - 19-12-2004 Yes, embedded linker directives in #pragma's are nice, however they don't allow the specification of undecorated names, that's why they have limited usefulness... For example, if this Code: #ifdef WIN32 #pragma comment(linker, "/EXPORT:GiveFnptrsToDll=_GiveFnptrsToDll@8,@1") #pragma comment(linker, "/SECTION:.data,RW") #endif works for metamod plugins, it doesn't for hook DLLs. I believe MSVC doesn't decorate GiveFnptrsToDll the same way. And that sucks a bit. Anyway, it's not a MSVC-specific problem, any C++ compiler decorates function names to resolve overload ambiguities. RACC home - Bots-United: beer, babies & bots (especially the latter) "Learn to think by yourself, else others will do it for you."