1 |
On Sun, May 06, 2012 at 08:42:34PM +0100, Ciaran McCreesh wrote: |
2 |
> On Sun, 6 May 2012 21:40:42 +0200 |
3 |
> Ulrich Mueller <ulm@g.o> wrote: |
4 |
> > > It's easy to miss some places that have to be updated when adding a |
5 |
> > > new EAPI. This hack fixes that. It works like this: |
6 |
> > |
7 |
> > > In pms.tex, at the top, we say |
8 |
> > |
9 |
> > > \CurrentEAPIIs{4} |
10 |
> > |
11 |
> > > Then everywhere where we have EAPI dependent content, we put |
12 |
> > |
13 |
> > > \ChangeWhenAddingAnEAPI{4} |
14 |
> > |
15 |
> > > which we can then grep for. Also, if you change the current EAPI, |
16 |
> > > and forget to change any of the markers, an error is produced. |
17 |
> > |
18 |
> > This looks a bit over-engineered to me. Wouldn't simple comments serve |
19 |
> > the same purpose? |
20 |
> |
21 |
> Comments don't force a failure when you forget about them. Being |
22 |
> self-validating makes it hard to screw up accidentally. |
23 |
|
24 |
Seconded; in the sphinx version of pms I've been playing w/ I was |
25 |
planning on using similar functionality (including deprecation markers |
26 |
so we make damn sure we remove stuff in later eapi's). |
27 |
~brian |