I'm in a long-standing situation with my module development where I
want to design a set of associated classes such that invocations of
submethods or class methods, such as new(), of one class by another
class continue to work as expected when any or all of those classes
is subclassed. I have
On Wed, Oct 19, 2005 at 03:11:21PM -0700, Darren Duncan wrote:
: What are some best practices here that can be used by anyone faced by
: a similar problem?
My battery's running low, so I just skimmed your article, but
my impression is that this is something that would be handled by
virtualizing
Darren,
Your problem reminds me of the Expression Problem, which is
something that IIRC Luke's Theory idea was trying to solve. Here is
the link to a paper Luke referred me to on the subject:
http://scala.epfl.ch/docu/files/IC_TECH_REPORT_200433.pdf
Also, you can Google the phrase
On 10/19/05, Darren Duncan [EMAIL PROTECTED] wrote:
[snip]
An example of when this situation can arise is if person X implements
a simplified XML DOM implementation using 2 classes, Document and
Node, that work together, where one of those classes (Document) can
create objects of the other
