Exactly. Which I cannot do because these classes are public and our customers rely on them. If I break the graph, that means changing a behavior that a customer might be using, and that would be a serious problem.
I am pushing to deprecate the entire graph and provide a completely different api that won't have these problems, but even if I get that approved, we have to support this for several releases. If there's an alternative, I'm all ears. On Jul 24, 2013, at 10:38 PM, Barrie Treloar <[email protected]> wrote: > On 25 July 2013 12:06, Russell Gold <[email protected]> wrote: >> Or let me rephrase that. In simple terms, I have dependency graphs like this: >> >> A ----> B ----> C >> ^ | >> \------- D <----/ >> >> How do I put these classes into separate modules? > > Short answer is: > Break the graph. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > ----------------- Come read my webnovel, Take a Lemon <http://www.takealemon.com>, and listen to the Misfile radio play <http://www.gold-family.us/audio/misfile.html>!
