Hello Simone,
It would be much more naturally to my hears hearing it as BigDecimalOrderedMonoid, doesn't it?
you have a valid point. However my intention is to decouple implementations from underlying interfaces, because they might evolve and grow over time.
Let me give you two examples: * Doubles can also be multiplied, but so far we did not need to include that in our stack of operations and properties. If we ever need to do so, it will be enough to create another interface extending OrderedMonoid and change the implemented interface in DoubleWeightOperations. * Also, there might be properties and/or operations that are unrelated to each other, hence DoubleWeightOperations might implement more than one interface in the future. How does that sound? Ciao, Claudio -- Claudio Squarcella PhD student at Roma Tre University http://www.dia.uniroma3.it/~squarcel http://squarcella.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
