[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jacorb-bugs
Subject:    [jacorb-bugs] [Bug 601] New: IDL compiler fails for typedef within
From:       bugzilla-daemon () inf ! fu-berlin ! de
Date:       2005-06-02 23:33:50
Message-ID: E1DdzCA-0007UX-00 () berners ! inf ! fu-berlin ! de
[Download RAW message or body]

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=601

           Summary: IDL compiler fails for typedef within valuetype
                    declaration
           Product: JacORB
           Version: 2.2.1
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: IDL compiler
        AssignedTo: gerald.brose@acm.org
        ReportedBy: dcalk@dejazzd.com
         QAContact: jacorb-bugs@lists.spline.inf.fu-berlin.de
                CC: dcalk@dejazzd.com


Using JacORB v2.2.2 (not available as a choice in Bugzilla Version field).  
Attempted to compile IDL containing the below:

    valuetype StrMapRelation : StrMapBase {
		struct Item {
			string key;
			ObjectReference ref;
			};
		typedef sequence <Item> ItemSeq;
		private ItemSeq m_refs;

		boolean is_composition();
		};

The following error is reported:

[jacorb.idl] ERROR : dds_dlrl.idl, line:513(18): Undefined name: 
DDS.StrMapRelation.StrMapRelation.ItemSeq
Can't recover from previous error(s), giving up.
                        private ItemSeq

Moving the typedef outside the valuetype declaration fixes the problem.  i.e., 
the below compiles successfully:

      struct Item {
         string key;
         ObjectReference ref;
         };
      typedef sequence <Item> ItemSeq;

    valuetype StrMapRelation : StrMapBase {
		private ItemSeq m_refs;

		boolean is_composition();
		};

The excerps shown above are taken from the DDS DLRL IDL which is an attachment 
to the OMG DDS specification (see http://www.omg.org/cgi-bin/doc?ptc/2004-04-
14).  I'm attempting to compile them for use with JacORB.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


[prev in list] [next in list] [prev in thread] [next in thread]