1 |
On Fri, 05 Mar 2010 13:12:36 +0200 |
2 |
Petteri Räty <betelgeuse@g.o> wrote: |
3 |
|
4 |
> Because there is so little benefit from removing old functions. What is |
5 |
> so bad about having them grouped at the bottom of the file inside a |
6 |
> deprecated section? |
7 |
|
8 |
Because then people use them. Don't ask me why. I have things I deprecated |
9 |
over two years ago still being used by a dozen ebuilds bumped within the last |
10 |
three months. You should be familiar with this behaviour wrt. |
11 |
built_with_use. So, when I'm making changes I still have to maintain the |
12 |
deprecated stuff. |
13 |
|
14 |
If I really want to get rid of it, then I have to break it. Replace the |
15 |
whole thing with a eerror like any of our deprecated eclasses. At that |
16 |
point, I would rather just remove the function or eclass than curate a museum |
17 |
of dead interfaces. But I suppose that's a personal quirk -- I hate having |
18 |
old unused code around. |
19 |
|
20 |
|
21 |
-- |
22 |
fonts, by design, by neglect |
23 |
gcc-porting, for a fact or just for effect |
24 |
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |