I understood you very well. That is why I wrote: "Please file an
issue." :)
-Stephan
LiZhan(李湛) wrote:
sorry, I thought that u might misunderstand me.
I mean that: In cppu/inc/uno/lbnames.h:1.20, the TMP_CPPU_ENV should not be
undefined.
Because that will cause I get a wrong string "TMP_CPPU_ENV" when I reference
CPPU_CURRENT_LANGUAGE_BINDING_NAME macro in my uno component written in VC9 like that:
__declspec(dllexport) void SAL_CALL
component_getImplementationEnvironment(
sal_Char const ** ppEnvTypeName, uno_Environment ** ppEnv )
{
*ppEnvTypeName = CPPU_CURRENT_LANGUAGE_BINDING_NAME;
}
Now, the pointer *ppEnvTypeName points to the string" TMP_CPPU_ENV " not "msci"
as expected.
Then it will fail, when I load the component through uno.exe.
-----邮件原件-----
发件人: Stephan Bergmann [mailto:[EMAIL PROTECTED]
发送时间: 2008年5月13日 19:12
收件人: [email protected]
主题: Re: [dev] I thought that it was a bug
LiZhan(李湛) wrote:
In openoffice.org_2.4_sdk\include\uno\lbnames.h
[...]
#undef TMP_CPPU_ENV //it should be commeted, otherwise it would cause
CPPU_CURRENT_LANGUAGE_BINDING_NAME macro generate TMP_CPPU_ENV, In
Visual C++ 2008, not expected as msci. Because the TMP_CPPU_ENV was
undefined when reference the macro
CPPU_CURRENT_LANGUAGE_BINDING_NAME.
Yes, cppu/inc/uno/lbnames.h:1.14.8.1 "missing undef" was obviously a
mistake. Please file an issue. (The reason this was not noticed before
is probably that in an OOo build CPPU_ENV is set to the correct value
via solenv/inc/target.mk:1.207 l. 1450 and/or
solenv/inc/tg_compv.mk:1.22 l. 145, anyway.)
-Stephan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
