Re: [racket] How to document a package and access its documentation

2013-08-13 Thread Lawrence Woodman
On 13/08/13 13:44, Matthew Flatt wrote: At Tue, 13 Aug 2013 11:15:10 +0100, Lawrence Woodman wrote: However, despite being able to render the docs with scribble, I still can't render with raco setup/ raco pkg install. When I try, I get the following error: raco setup: --- building docume

Re: [racket] Peekable asynchronous channel?

2013-08-13 Thread Robby Findler
You need a single thread that mediates access to the "peek state". It will be fine, and thread-safe if you do it that way and you can even make it kill-safe if you want. (You'll get a whole new set of channels for doing the communication.) Robby On Tue, Aug 13, 2013 at 9:48 AM, Jonathan Schuster

Re: [racket] How to document a package and access its documentation

2013-08-13 Thread Lawrence Woodman
On 13/08/13 13:57, Jay McCarthy wrote: On Tue, Aug 13, 2013 at 3:47 AM, Lawrence Woodman wrote: On 12/08/13 15:08, Jay McCarthy wrote: Packages do not have documentation, but collections inside of packages may have documentation. However, if you have a single collection package, then the info

Re: [racket] Peekable asynchronous channel?

2013-08-13 Thread Jonathan Schuster
Thanks for the feedback, all. Wrapping the channel with my own custom logic was definitely the approach I was thinking about if I wrote it on my own, so I'm going forward with that. Having thought about it more, even without getting the peeked value this wrapper wouldn't be thread-safe: one thread

Re: [racket] How to document a package and access its documentation

2013-08-13 Thread Jay McCarthy
On Tue, Aug 13, 2013 at 3:47 AM, Lawrence Woodman wrote: > On 12/08/13 15:08, Jay McCarthy wrote: >> >> Packages do not have documentation, but collections inside of packages >> may have documentation. >> >> However, if you have a single collection package, then the info file >> is for both the pa

Re: [racket] How to document a package and access its documentation

2013-08-13 Thread Matthew Flatt
At Tue, 13 Aug 2013 11:15:10 +0100, Lawrence Woodman wrote: > However, despite being able to render the docs with scribble, I still > can't render with > raco setup/ raco pkg install. When I try, I get the following error: > > raco setup: --- building documentation --- > raco setup: do

Re: [racket] How to document a package and access its documentation

2013-08-13 Thread Lawrence Woodman
Hello all, Thanks for the suggestions and for directing me to raco docs, which I hadn't come across previously. I have been able to render the scribble files and push them to github pages. I then pointed to this from the README file and set the project's homepage link to also point here. T

Re: [racket] How to document a package and access its documentation

2013-08-13 Thread Lawrence Woodman
On 12/08/13 15:08, Jay McCarthy wrote: Packages do not have documentation, but collections inside of packages may have documentation. However, if you have a single collection package, then the info file is for both the package and the collection metadata. In my package I have the following dir