2013/5/6 Thien-Thi Nguyen <t...@gnu.org> > () Panicz Maciej Godek <godek.mac...@gmail.com> > () Mon, 6 May 2013 21:36:33 +0200 > > Thanks :) I see that there are a few persons with similar ideas, and > I wonder how powerful we'd become if we managed to orchestrate our > powers somehow, as TTN suggested > > Orchestration is a nice concept. It is the marshalling of separate > efforts in a parallel direction (towards the audience), moderated > individually, but w/ group awareness, by precise changes in timing and > pitch. Cool. > > For this, i strongly urge everyone who wants to jam[0] to provide > documentation. That is the minimal requirement, the tuning of your > instrument so that it does not burn the ears of others seated beside > you. So what if you don't have (the autotools) rhythm? That can (and > must!) be cyclically attained. To start, you gotta have the right Hz. > > "But ttn, documentation is a pain to create and maintain!" > > Well, yes. For creation, i offer as riposte Guile-BAUX[1], > [...]
This looks truly awesome! However, I'm only getting acquainted with autotools, and there are many secrets to me. I see that both guile-sdl and guile-figl copy the scm modules to $(prefix)/share/guile/site..., but apparently they both do that in a different way (which means there's no standard way), and none of them allows to 'fine tune' that directory with an optarg to ./configure And the whole thing makes me wonder about the status of guile documentation. The guide is really great (although sometimes it remains silent about certain features that can be found in header files), but I've observed that doc-strings for built-in functions are no longer available, even though they are specified. And besides, how do the aforementioned modules (those are, as I reckon, tsar and c-tsar) refer to guile-snarf-docs that is shipped with guile source? The nice thing (IMNSHO) is that Guile-BAUX is itself a nontrivial chunk > of Guile Scheme, nothing more, and furthermore takes pains to rise above > the cacaphony of Guile version-specific quirks. > > Documentation maintenance, on the other hand, is a charge laid squarely > on the Author and the Author's discipline and astuteness. You know what > to do; you know how to do it; what must be dredged from the void is the > will and the practice, the mind and the motion. I wish you fortitude. > Well, thanks, I'll do my best :)
