1 |
Dnia 2014-07-04, o godz. 11:26:01 |
2 |
Ulrich Mueller <ulm@g.o> napisał(a): |
3 |
|
4 |
> Since names like _USER or _PAM look a little dangerous, I suggest |
5 |
> _<eclassname>_ECLASS for the variable's name. |
6 |
> |
7 |
> I have no strong preference for the variable's value. Is testing for |
8 |
> a non-empty value sufficient? Then we should assign something simple |
9 |
> (like "1"). If not, any string that is sufficiently random (like the |
10 |
> one used in eutils) should be good. |
11 |
|
12 |
I'd rather go for simple value and simple test. Exact tests with weird |
13 |
names are more prone to mistakes, and this is not something you usually |
14 |
test. |
15 |
|
16 |
While at it, I would also like to ask all eclasses to keep |
17 |
EXPORT_FUNCTIONS *outside* the ifs to keep the exports consistent with |
18 |
inherits. Otherwise, indirect inheritance influences effectively |
19 |
exported phase functions and changes in 'inherit' order may affect |
20 |
exported functions seemingly randomly. |
21 |
|
22 |
-- |
23 |
Best regards, |
24 |
Michał Górny |