<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - osl_getEnvironment wrapper ..." href="https://bugs.documentfoundation.org/show_bug.cgi?id=124799#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - osl_getEnvironment wrapper ..." href="https://bugs.documentfoundation.org/show_bug.cgi?id=124799">bug 124799</a> from <a class="email" href="mailto:sbergman@redhat.com" title="Stephan Bergmann <sbergman@redhat.com>"> Stephan Bergmann</a> <pre>An include/osl/process.hxx C++ wrapper is curiously missing indeed. However: * If we add one, it should probably cover C++ wrappers for all (or at least most) of the include/osl/process.h C functionality. * Even though that would be inline functions, we would need to get them right "on first shot", because MSVC tends to export even such inline functions from the __declspec(dllexport) DLL (and rely on that from __declspec(dllimport)'ing DLLs). * osl_getEnvironment returns oslProcessError, the C++ wrapper should probably return such an error code too (if only to be able to distinguish between unset and empty env vars). * An optionalDefault brings up the question whether it should be returned only for unset or also for empty env vars. Different callers may have different needs/expectations, and I'm not sure whether such an optional arg would be worth it anyway.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>