Parser2 considered harmful

[Miles Sabin]

John Cowan wrote,
> If they do inherit, then you have the problem that 
> Parser may be extended in several logically distinct 
> ways, leading to interfaces Parser2A and Parser2B.  
> The next generation will have to specify Parser3A, B, 
> and C all inheriting from Parser2A *and* Parser2B, 
> which causes a messy diamond-shaped inheritance graph.

It's not diamond inheritance per-se which is the
problem, it's (as you point out) the potential for a
combinatorial explosion of derived interfaces which is
nasty.

Cheers,


Miles

-- 
Miles Sabin                          Cromwell Media
Internet Systems Architect           5/6 Glenthorne Mews
+44 (0)181 410 2230                  London, W6 0LJ
msabin at cromwellmedia.co.uk           England



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)