On 6/20/15, 10:08 AM, "Michael Schmalle" <teotigraphix...@gmail.com> wrote:
>But won't you start to have conflicts if you wanted other libraries that >used mixins? Yes, if you have a stack of swcs each trying to modify a class definition in incompatible ways, then our current compiler won’t like it. Now it is currently true that you can have N different versions of a class scattered through your swcs and the compiler will check the time stamp in the catalog.xml and always pull the most recent one. We could try to leverage that, or inject something in the catalog.xml so that there is a way to choose which conflicting version wins. And/or, we could simply allow modification of a class by merging the APIs from all of the definitions found in the various SWCs, since that is allowed in the browser. You probably still need a deterministic way of knowing which conflict wins. But for now, baking all of js.swc with JQuery’s modifications into jquery.swc will hopefully get us pretty far. -Alex
