The simplest case I can think of is a relationship: class A refers to class B, while class B refers to A. You don't know which is the one to compile first. But you could have class A which refers to B, B to C, and C to A, using array of references.
As Ram�n said, it's not only a case of subclassing (which is obviously one way only), but also of properties, method definitions, SQL, etc. Max "Denver Braughler" <[EMAIL PROTECTED]> ha scritto nel messaggio news:[EMAIL PROTECTED] > Max Sebastiani wrote: > > Denver Braughler ha scritto nel messaggio: > >> Max Sebastiani wrote: > >>> (there are many classes which depend each other) > >> Why? > > A circular reference. > < Why? > << Because classes depend each other. > <<< Why? > <<<< See above. > > Would you offer to me an example of a desirable circular reference?
