7 |
definitely, digging through mailing list archives is suboptimal. once i get |
definitely, digging through mailing list archives is suboptimal. once i get |
8 |
1.4.1 (and .2, etc, if required) out, i'll organize an archeological dig to |
1.4.1 (and .2, etc, if required) out, i'll organize an archeological dig to |
9 |
get all the proper bits (and xref) locked down. |
get all the proper bits (and xref) locked down. |
10 |
|
|
11 |
|
* 2002/02/23 19:58:56 ttn |
12 |
|
|
13 |
|
well, now i think xref is "under the treshold" for minimal reflection; i.e., |
14 |
|
1.4.1 doc/guile-api.alist needs xref annotation. this doesn't excuse api-diff |
15 |
|
from needing to handle un-annotated entries, however. |
16 |
|
|
17 |
|
although logically, separation implies reduced dependencies, so that cutting |
18 |
|
ourselves slack is feasible (by not making 1.4.1 release dependent on x.a.), |
19 |
|
it's no big deal to do (grep+lambda); archeology isn't that bad if it involves |
20 |
|
writing simple tools and applying them. |
21 |
|
|
22 |
|
this is being more careful by using guile. |
23 |
|
|