On Wednesday 27 February 2002 05:20 am, Nathanael Schärli wrote:

> a) Whenever someone wants to use two mixins with the same selector x, the
> browser shows this selector in a special category "-- conflicts --" and
> defines it as "self error: 'Mixin conflict!'" per default. This means that
> the programmer has to resolve the conflict himself.
>
> b) When two mixin define the same selector, they cannot be used in the same
> class

Given that one can add or change methods at any time, when would the mixin 
conflicts be detected? Would you require an analysis of the entire system 
every time a class or method changed?

-- 
Ned Konz
currently: Stanwood, WA
email:     ned at bike-nomad.com
homepage:  http://bike-nomad.com