[orbitcpp-list] questions

[Andreas K. <ak...@ix...>]

Hi Phil,

got some questions regarding the runtime:

* why the extra op_marshaller method in the skels? why not everything in
one skel wrapper?
* are you sure the environment singleton does not cause reentrancy
problems (e.g. a calls b and b calls a back before returning) apart from
being not thread-safe (aka: is creating the env on the stack much more
inefficient?)
* what specifically was the problem with keeping servants on the stack?
(it worked for o2cpp)
* shouldn't we prefix every non-spec method in public inheritable
classes by something like _orbitcpp to reduce the risk of name clashes?
* shouldn't we reindent this with indent-namespaces on? (if yes, go
ahead, see .astylerc from other mail)

* do you still have a copy of o2cpp handy? if yes, have a look at the
following:
- lang_c.cc: duplicateGuarded,releaseGuarded. prevents missing
exceptions.
- o2cpp_smartptr.hh: what about taking this implementation instead of
all the "nicked from mico&omniorb" stuff? (pro: wchar support, nice and
consistent; con: breaks existing code)
- o2cpp_exception.hh: looks more complete than yours

that's it for tonight. i'm getting some sleep.

cya
andy