[omniORB] issue - omniORB-4.1.5 - code generation

Duncan Grisby duncan at grisby.org
Fri Dec 21 14:10:43 GMT 2012


On Wed, 2012-12-12 at 09:18 -0800, Manas wrote:

[...]
> abstract valuetype A
> {
>   string name();
> };
> typedef sequence<A> ASeq;
> 
> IDL compilation is fine, but when I try to compile the generated
> stubs/skeleton, it doesn't compile. 
> It looks, the reason behined is it has generated a arry of 0 elements,
> which compiler doesn't like and it looks like is bug.
> static CORBA::PR_valueMember _0RL_valuemember_A[] = {
>   
> };

That is indeed a bug. The code compiles fine with some compilers, but
not Visual C++. The fix was already in the trunk branch, but I've
back-ported it to 4.1.x and checked it in to the 4_1_develop branch.
Here's a patch that fixes it.

Cheers,

Duncan.

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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: empty_valuemember.patch
Type: text/x-patch
Size: 1422 bytes
Desc: not available
URL: <http://www.omniorb-support.com/pipermail/omniorb-list/attachments/20121221/71ac7301/attachment.bin>


More information about the omniORB-list mailing list