ICE forward decls

PeteHPeteH Peter HugOrganization: Warehouse Optimization LLCProject: APALMember ✭✭
While slice2cpp processes the following two ice modules successfully, it implements the classes IA::__U__As and IB::__U__Bs in a.h and b.h causing compile errors.

How can I avoid this without merging all the ice modules into one?

a.ice
module IA
{
  interface A;
  sequence<A*> As;
};

module IB
{
  interface B;
  sequence<B*> Bs;
};

module IA
{
  interface A
  {
    As     GetAs();
    IB::Bs GetBs();
  };
};
b.ice
module IB
{
  interface B;
  sequence<B*> Bs;
};

module IA
{
  interface A;
  sequence<A*> As;
};

module IB
{
  interface B
  {
    Bs     GetBs();
    IA::As GetAs();
  };
};

Comments

  • matthewmatthew NL, CanadaMatthew NewhookOrganization: ZeroC, Inc.Project: Internet Communications EngineMember ✭✭✭
    You should put the common types into a slice file and #include it from the other files.

    ie:

    seqtypes.ice
    module IA
    {
      interface A;
      sequence<A*> As;
    };
    
    module IB
    {
      interface B;
      sequence<B*> Bs;
    };
    

    a.ice
    #include <seqtypes.ice>
    
    module IA
    {
      interface A
      {
        As     GetAs();
        IB::Bs GetBs();
      };
    };
    
  • PeteHPeteH Peter HugOrganization: Warehouse Optimization LLCProject: APALMember ✭✭
    Thanks, but this doesn't really help in my case :(

    The problem is that I wanted further modules based on a.ice and b.ice. So if I build somethhing like atypes.ice and btypes.ice and include both of these in both a.ice and b.ice, i can compile all ice files correctly.

    Now if I add a1.ice like so:
    #include <a.ice>
    
    module IA
    {
      interface A1 extends A
      {
        As     booh();
        IB::Bs baah();
      };
    };
    

    It won't compile because slice basically ignores the #include <a.ice>.
  • matthewmatthew NL, CanadaMatthew NewhookOrganization: ZeroC, Inc.Project: Internet Communications EngineMember ✭✭✭
    What exactly do you mean by slice ignores the include of a.ice? For C++ #include <a.ice> generates to #include <a.h>. Thefore you must compile not only a1.cpp but also a.cpp.
  • marcmarc FloridaMarc LaukienOrganization: ZeroC, Inc.Project: The Internet Communications EngineAdministrators, ZeroC Staff ZeroC Staff
    I don't understand what you mean with "ignores #include<a.ice>". Can you elaborate?

    Ice follows C++: You can have multiple declarations of types, but you can only define types once.
  • PeteHPeteH Peter HugOrganization: Warehouse Optimization LLCProject: APALMember ✭✭
    Sorry, I got this all wrong. My problem was that I misspelled the module name in c.ice so slice2cpp didn't recognise interface A. Therefore, including a.ice or not had no impact. I thought the problem had to do with slice2cpp not handling nested includes.

    Thanks for your help.
Sign In or Register to comment.