Niclas Hedhman wrote: > Ok, good convenience here. What about "visibility" ?? Will the > ValueBuilder be chosen with the visibility of the ValueComposite being > mutated, or the client doing the action? > The former sounds more correct or at least intuitive, but are we then > not "leaking concerns" ??
The builder will be from the same module as the value that is being modified. Yes, I think this is a "leaking concern" in the sense that it should be a "context mixin" rather than "static mixin", if you compare with what I just wrote to Peter about the Scala presentation. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
