On Wed, 14 Jun 2006 email@example.com wrote:
On Jun 13, 2006, at 10:38 AM, Yukihiro M. wrote:
I don’t think I understand you. Do you want to allow #include to
include classes? Without making it MI? Hmm.
It isn’t altogether obvious to me why a class passed to #include couldn’t be
interpreted as a module (since instances of Class are instances of Module
with classes, this is always the situation. obviously it can be
with - but it’s a little less straight forward than the ‘normal’ mixin
not for or against here - but i do believe being able to mixin classes,
without some really slick handling of super/initialize, state, and
on ruby’s part would be confusing for most. in otherwords, ruby would
become mi to do so.