[omniORB] strange omniidl c++ result

[Duncan Grisby]

On Friday 23 July, Rene Jager wrote:

> >  If the array is defined inside an interface,
> > the functions are defined in a C++ class, so they really do need to be
> > static. Similarly, omniORB still supports archaic compilers that have
> > no namespace support, meaning IDL modules are mapped to C++ classes,
> > again requiring the static.
> 
> so "static inline" would always work then?

Yes it would, but the static would be redundant when it's inside a
namespace. With the fix I've done, it's only there if it's needed.
The old generated code also generated extern functions for arrays at
global scope, for no obviously good reason.

Cheers,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan at grisby.org     --
   -- http://www.grisby.org --