What you have is a design problem. If A needs B to exist, and B needs A to
exist, then either
- There is some other implicit object that provides data to both A and B,
or
- You really have one logical class, and your implementation is trying to
pretend it's two
The most straightforward way
If I read the example correctly. B does not need A. It just provides a method
to retrieve a new instance of A.
So A and B should really be 2 separate classes.
Am 23. Dezember 2014 03:10:12 MEZ, schrieb Tim Boudreau niftin...@gmail.com:
What you have is a design problem. If A needs B to exist,
