Re: 2 classes, 1 method

earthwormgaz <earthwormgaz@googlemail.com> wrote in news:ecab2b90-d045-
46eb-aef2-de876d6ee590@z72g2000hsb.googlegroups.com:


You can always refactor it (and the data it needs) into a base class and
inherit that from both (privately if it's an implementation detail
only).

class base {
public:
  methodIDoNeed(){}
private:
  // data needed by methodIDoNeed()
};

class A : private /* or public */ base {
  doStuffIDon'tCareAbout(){}
};

class SlimA : private base {
};

Or, if SlimA is a true subset of A, then just move stuff to SlimA, and
inherit SlimA from A.

class SlimA {
public:
  methodIDoNeed(){}
private:
  // data needed by methodIDoNeed()
};

class A : private /* or public */ SlimA {
  doStuffIDon'tCareAbout(){}
};

That will get you code sharing anyway. Be careful with these kinds of
refactorings though. If you aren't careful to keep thing logically
meaningful, you can end up with a spaghetti-like mess and not be able to
make heads or tails of anything.

If you just want a smaller interface to the existing A, then you define
an abstract base class with the interface you want, inherit that
publicly in A and make your methods etc use the interface instead of A.

class ISlimA {
public:
  virtual ~ISlimA(){}
  virtual methodIDoNeed() = 0;
};

class A : public ISlimA {
  doStuffIDontCareAbout() { } // loads of these
  methodIDoNeed() { }
};

A a;

ISlimA & sa = a;
..
..
..

I didn't actually compile any of the above, but I think it's right.

HTH,
joe