salut louis > > One hopes that it can progress in tandem with the code, by > > necessity a bit behind cutting-edge features > > > Actually, shouldn't that be the way around? Documenting is thinking. > We can look at this from two ends. Case #1 The program exists and it > is (partially) or (not well) documented, hence the necessity to > explain afterwards — and this comes naturally, yes, behind. Case #2 > We can think of a more integrated way of doing things where any idea > or feature or enhancement that makes it into the application is first > well-thought of, defined, described, thus truly documented before it > is actually coded.
this is exactly what i thought while reading greg's words :-) not easy to do, but an idea worth to be seriously considered! ciao a.l.e _______________________________________________ CREATE mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/create
