On May 26, 2008, at 4:30 PM, Bryan Duxbury wrote:
I'm also seeing attempts to mimic Interfaces/virtual classes,
which is
just plain ugly (see TProtocol where every method returns nil).
As long as there is a nice way of documenting what methods are
expected
to be implemented in the concrete subclasses.
I would be happy with the "abstract" methods raising exceptions when
they're called. I think their definitions should still live though,
and perhaps with a little RDoc to actually explain their purposes.
That does have the benefit of showing the method listing in rdoc, but
as long as we bundle at least one concrete implementation of each
"abstract" class, that same goal will be achieved just by documenting
the methods on the concrete implementation. I could go either way on
this one (though I would prefer not to have the dummy methods),
because the most important aspect here is that unimplemented methods
should raise an exception.
-Kevin
--
Kevin Ballard
[EMAIL PROTECTED]
