This is the mail archive of the guile@cygnus.com mailing list for the guile project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
jimb@red-bean.com writes: > > That's persuasive. But I'm still hung up on the fact that I'll either > have to document every Scheme-visible scm_ function twice, or have one > section just be cheezy and refer the reader to another section of the > manual. > > That, combined with the appeal of organizing the manual strictly by > functionality, and the thought that people can ignore the languages > they don't care about, are what make me like the organization I > proposed. > > If you can suggest a good solution to the duplication problem, I might > change my mind. Find a clever way to process the same files twice and output either a C manual or a Scheme manual. I don't know that much about texinfo, but TeX itself is turing complete. If hacking macros to do this is impossible or undesirable, some minimally intelligent preprocessing layer should be able to handle it. I can even think of ways to do it with cpp, the world's lamest preprocessor. - Maciej