| 1 |
On Thu, 24 May 2012 14:02:05 +0100 |
| 2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
|
| 4 |
> On Thu, 24 May 2012 00:02:37 -0600 |
| 5 |
> Ryan Hill <dirtyepic@g.o> wrote: |
| 6 |
> > I don't see how removing an inherit is breaking an eclass' API. |
| 7 |
> |
| 8 |
> The way eclasses are defined, the eclasses it inherits are itself part |
| 9 |
> of its API. You can think of it using the lousy OO analogy that gave |
| 10 |
> eclasses their name: the (public) superclasses of a class are part of |
| 11 |
> its API. |
| 12 |
|
| 13 |
Like I said, technically it is. And that's terrible. Let's ignore it. :D |
| 14 |
|
| 15 |
|
| 16 |
-- |
| 17 |
fonts, gcc-porting |
| 18 |
toolchain, wxwidgets |
| 19 |
@ gentoo.org |
Archives