Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
On Thu, 24 May 2012 00:02:37 -0600
Ryan Hill <dirtyepic@g.o> wrote:
> I don't see how removing an inherit is breaking an eclass' API.
The way eclasses are defined, the eclasses it inherits are itself part
of its API. You can think of it using the lousy OO analogy that gave
eclasses their name: the (public) superclasses of a class are part of
its API.
--
Ciaran McCreesh
|
|
