Re: r6rs library documentation

2010-07-02 Thread Ludovic Courtès
Hi Julian! Julian Graham writes: >> How about this instead: >> >> �...@code{div} is an alias for Guile’s @code{quotient} and @code{mod} is >>  an alias for @code{modulo} (@pxref{Integer Operations}). > > Well, I don't know. Those exports currently /are/ aliases for those > procedures, but that'

Re: r6rs library documentation

2010-06-23 Thread Julian Graham
Hi Ludovic! > There’s no ‘fold’ in R6RS-lib; it’s called ‘fold-left’. Fixed -- see commit 5b379729bb5f5d06ceb02c4e96ccc62cf61f9c62. > Should be “Guile’s core library (@pxref{List Modification}).” Fixed. > How about this instead: > > �...@code{div} is an alias for Guile’s @code{quotient} and

Re: r6rs library documentation

2010-06-22 Thread Ludovic Courtès
Hi Julian, Julian Graham writes: >> Sounds great to me, though Brian & Neil can always come in to correct me >> :) > > Done! See commit ea28e981342fd1d381e489e57cddde97eb390442. In > addition to the main .texi payload, I adjusted the formatting on some > of your initial paragraphs and removed

Re: r6rs library documentation

2010-06-21 Thread Julian Graham
> Sounds great to me, though Brian & Neil can always come in to correct me > :) Done! See commit ea28e981342fd1d381e489e57cddde97eb390442. In addition to the main .texi payload, I adjusted the formatting on some of your initial paragraphs and removed the descriptions of the base and composite li

Re: r6rs library documentation

2010-06-21 Thread Andy Wingo
Heya, On Sun 20 Jun 2010 23:23, Julian Graham writes: >> I think that Neil would probably have the most useful feedback, as I >> think he has the most global view of the manual. I am inclined to think >> that the level of detail is appropriate, though I imagine that Neil and >> Brian are cringin

Re: r6rs library documentation

2010-06-20 Thread Julian Graham
Hey Andy, > I think that Neil would probably have the most useful feedback, as I > think he has the most global view of the manual. I am inclined to think > that the level of detail is appropriate, though I imagine that Neil and > Brian are cringing at the weight of the extra pages on the press ;

Re: r6rs library documentation

2010-06-14 Thread Andy Wingo
Hi Julian, On Sat 12 Jun 2010 21:32, Julian Graham writes: > As promised, I've got an initial draft of the standard libraries > documentation done. Very cool! > Although I tried to avoid reproducing the content > of `r6rs-lib', it's still a bit more verbose, I think, than what we > discussed

Re: r6rs library documentation

2010-06-12 Thread Julian Graham
Hi Guilers, As promised, I've got an initial draft of the standard libraries documentation done. Although I tried to avoid reproducing the content of `r6rs-lib', it's still a bit more verbose, I think, than what we discussed earlier in this thread (the Texinfo file clocks in at ~83k), so I could

Re: r6rs library documentation

2010-06-05 Thread Julian Graham
Hi all, > Works for me.  I'll get started on these soon. Status update: I'm still working on the standard libraries documentation -- I'd say I'm about 70% done. I should have a draft to email out in the next week or so. Regards, Julian

Re: r6rs library documentation

2010-05-08 Thread Julian Graham
Hi Ludovic, >> My initial feeling is that there are two documentation sections to be >> created: A description of Guile's implementation of the R6RS `library' >> and `import' forms; and some notes on the bits of the R6RS "Standard >> Libraries" that Guile provides, along with pointers to more for

Re: r6rs library documentation

2010-05-05 Thread Ludovic Courtès
Hi Julian! Julian Graham writes: > As per Andy's suggestion, I'd like to start adding some documentation > for the R6RS library code Ive been working on, and I wanted to get a > sense of where that documentation should go. Nice! > My initial feeling is that there are two documentation sections

r6rs library documentation

2010-05-05 Thread Julian Graham
Hi Guilers, As per Andy's suggestion, I'd like to start adding some documentation for the R6RS library code Ive been working on, and I wanted to get a sense of where that documentation should go. My initial feeling is that there are two documentation sections to be created: A description of Guile