Object.mixin( source, target ) | arguments changed

Andrea Giammarchi andrea.giammarchi at gmail.com
Thu Jun 13 16:17:32 PDT 2013


Rick talked about a third argument but if that won't exist I like multiple
sources too.

It's also more suitable as Object.mixin(target, ...[source1, source2,
source3]) for predefined collections of mixins to reuse

+1 here


On Thu, Jun 13, 2013 at 3:57 PM, Dmitry Soshnikov <
dmitry.soshnikov at gmail.com> wrote:

>
> On Thu, Jun 13, 2013 at 2:38 PM, Brendan Eich <brendan at mozilla.com> wrote:
>
>> Allen Wirfs-Brock wrote:
>>
>>> I personally don't see that there is any real conflict between
>>> Object.mixin and a hypothetical "mixin" superclass combinator that someone
>>> might define in the future.
>>>
>>
>> What about multiple sources? That might take almost all the perceived
>> conflict away.
>>
>>
> The question which help to solve is: "Why _not_ to have multiple sources?"
> If there are strong concerns, then one source is the way, otherwise
> multiple sources seems more functional.
>
> Dmitry
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20130613/f3701ec8/attachment.html>


More information about the es-discuss mailing list