Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You'll have to put a virtual method on BaseClass to call processObj from the derived classes.</p> <pre><code>class BaseClass{ public: BaseClass(){} virtual void ProcessThis(Processor &amp;p) { p.processObj(this); } virtual void myFunction(){cout &lt;&lt; "base myFunction called" &lt;&lt; endl;} }; class Derived1: public BaseClass{ public: Derived1():BaseClass(){} void ProcessThis(Processor &amp;p) { p.processObj(this); } void myFunction(){cout &lt;&lt; "Derived1 myFunction called" &lt;&lt; endl;} }; class Derived2: public BaseClass{ public: Derived2():BaseClass(){} void ProcessThis(Processor &amp;p) { p.processObj(this); } void myFunction(){cout &lt;&lt; "Derived2 myFunction called" &lt;&lt; endl;} }; class Derived3: public BaseClass{ public: Derived3():BaseClass(){} void ProcessThis(Processor &amp;p) { p.processObj(this); } void myFunction(){cout &lt;&lt; "Derived3 myFunction called" &lt;&lt; endl;} }; class Processor{ public: Processor(){} virtual void processObj(BaseClass* bc){cout &lt;&lt; "got a base object" &lt;&lt; endl; bc-&gt;myFunction();} virtual void processObj(Derived1* d1){cout &lt;&lt; "got a derived1 object" &lt;&lt; endl; d1-&gt;myFunction();} virtual void processObj(Derived2* d2){cout &lt;&lt; "got a derived2 object" &lt;&lt; endl; d2-&gt;myFunction(); } }; int main() { BaseClass *bcp=new BaseClass(); Derived1 *dc1p=new Derived1(); Derived2 *dc2p=new Derived2(); Derived3 *dc3p=new Derived3(); Processor p;//can also use Processor* p = new Processor() //first set results bcp-&gt;ProcessThis(p); dc1p-&gt;ProcessThis(p); dc1p-&gt;ProcessThis(p); dc3p-&gt;ProcessThis(p); BaseClass *bcp1=bcp; BaseClass *dc1p1=dc1p; BaseClass *dc2p1=dc2p; BaseClass *dc3p1=dc3p; //second set results bcp1-&gt;ProcessThis(p); dc1p1-&gt;ProcessThis(p); dc2p1-&gt;ProcessThis(p); dc3p1-&gt;ProcessThis(p); Processor p2; bcp1-&gt;ProcessThis(p2); dc1p1-&gt;ProcessThis(p2); dc2p1-&gt;ProcessThis(p2); dc3p1-&gt;ProcessThis(p2); return 0; } </code></pre> <p>You basically want the Visitor pattern, but with only one type of visitor. You might save yourself some future effort and make Processor into an abstract class and implement the one concrete ProcessorImpl class, making it trivial to add another processor class in the future, or you could wait until that situation comes up and leave things as is for now.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload