Re: [racket-users] in-source documentation, single-file packages, and scribble/srcdoc

2018-01-28 Thread Neil Van Dyke
Deren Dohoda wrote on 01/27/2018 06:34 PM: If I understand the implication: how is turbo-racket practically different from scribble/lp2? —Just that the code is not put in the document? Put one way, I think literate programming is more about expressing the programmer's *how* of the module/pack

Re: [racket-users] in-source documentation, single-file packages, and scribble/srcdoc

2018-01-27 Thread Deren Dohoda
Neil, If I understand the implication: how is turbo-racket practically different from scribble/lp2? —Just that the code is not put in the document? Deren On Sat, Jan 27, 2018 at 7:26 AM, Neil Van Dyke wrote: > 1. Do we foresee using srcdoc for new work in the future, and is it > suitable as pa

Re: [racket-users] in-source documentation, single-file packages, and scribble/srcdoc

2018-01-27 Thread Tim Jervis
Dear Neil, I can’t respond to point 1; I don’t have sufficient knowledge of the options. However, I would very much like to endorse the idea behind point 2. Kind regards, Tim > On 27 Jan 2018, at 12:26, Neil Van Dyke wrote: > > 1. Do we foresee using srcdoc for new work in the future, and

[racket-users] in-source documentation, single-file packages, and scribble/srcdoc

2018-01-27 Thread Neil Van Dyke
1. Do we foresee using srcdoc for new work in the future, and is it suitable as part of a backend for other in-source documentation? 2. What do people think of writing reusable modules approximately like the example below?  Is that something you'd want to do? (The basic idea is that you usual