"Andrei Alexandrescu" <[EMAIL PROTECTED]> writes:
> "David Abrahams" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>> > Yes, a class is it's own superclass/subclass, but IMO not it's own
>> > base: so it is a bug in the implementation.
>>
>> I'd like to suggest changing the documentation to match the
>> implementation at this point. I know of a few places where I have
>> relied on the current semantics, and I'm sure that's the case for
>> others as well. I'm not set on this course, but I think it's worth
>> considering.
>
> At the cost of adding an extra name, maybe it would be nice to provide
> is_base_and_derived and is_super_and_subclass.
I could get behind that if I could quickly tell the difference in
semantics from those names, but I can't.
Also, I think there's a principle behind the boost type traits that
they reflect standard notions of the type system, (which doesn't
include "subclass"), so by that logic my idea of keeping the semantics
and changing the docs also seems kinda bogus. I guess I withdraw it.
--
David Abrahams
[EMAIL PROTECTED] * http://www.boost-consulting.com
Boost support, enhancements, training, and commercial distribution
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
