I was thinking of something that led into, say Quick, but was written for someone who was trying to figure out #lang. That is, a PLT newbie who wants to first learn about #lang lines and, even if they don't know it yet, second wants to do some tutorial.
But a second best would be changing the way that section is written up to be more #lang-centric. Robby On Fri, Jan 29, 2010 at 9:44 AM, Eli Barzilay <e...@barzilay.org> wrote: > On Jan 29, Robby Findler wrote: >> On Thu, Jan 28, 2010 at 4:52 PM, Ryan Culpepper <ry...@ccs.neu.edu> wrote: >> > Robby Findler wrote: >> >> >> >> Matthew suggested a change to the language dialog that I've just now >> >> checked in. Please give it a try and let me know what you think. >> > >> > I think the explanatory text under the first option should be replaced with >> > something like the following: >> > >> > Typical language declarations: >> > #lang <language-name> >> > #!r6rs >> > >> > Or perhaps instead of the abstract #lang example have two concrete ones, >> > like "#lang scheme" and "#lang typed/scheme". >> > >> > It should also have a link to an explanation of language declarations in >> > the >> > help desk, either following the examples or as the text "language >> > declarations" above hyperlinked. >> >> Does it make sense to have a link to an introduction that explains >> #lang (and moves on to other things) instead? > > I thought that something like > http://docs.plt-scheme.org/guide/Module_Syntax.html > would be right, except that this section needs some improvements, like > avoiding the `module' reference (or maybe explaining it much later > than the first sentence), and generally making it more beginner > friendly. > > -- > ((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay: > http://barzilay.org/ Maze is Life! > _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
