1 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
2 |
> On Tue, 24 Feb 2009 15:37:36 -0500 |
3 |
> Jim Ramsay <lack@g.o> wrote: |
4 |
> > > They only ended up nicely documented after people moaned a lot |
5 |
> > > that they were having a hard time keeping track of EAPIs... |
6 |
> > |
7 |
> > You can't possibly be suggesting that everyone will be able to keep |
8 |
> > an ever-increasing number of feature sets in his or her mind, or |
9 |
> > that changing from a two-level to a one-level EAPI definition will |
10 |
> > remove the need for documentation going forward, so I'm not sure |
11 |
> > what you mean by this. |
12 |
> |
13 |
> That's exactly what I mean. Developers can probably just about keep up |
14 |
> with the two or three EAPIs they'll ever be working with on a regular |
15 |
> basis, but they probably can't keep up with that if you double it. |
16 |
|
17 |
Well, if you're assuming only two or three EAPIs in 'mental cache' at |
18 |
any one time under glep-55, I'm not sure how this changes wrt. a |
19 |
two-level system. A two-level system doesn't change the number of |
20 |
EAPIs in the tree or available to developers, it just changes how they |
21 |
are named. |
22 |
|
23 |
Regardless, this does not remove the need for documentation. All |
24 |
the EAPIs should be documented in both the PMS and the devmanual. This |
25 |
makes it possible for new developers to learn about the current |
26 |
features available, and also helps existing devs who may need to |
27 |
recover from 'mental page faults' from time to time. |
28 |
|
29 |
-- |
30 |
Jim Ramsay |
31 |
Gentoo Developer (rox/fluxbox/gkrellm/vim) |