If you read the documentation as a textbook when you start programming, I can see wanting to see something that says "cond is the same as before". But, if you read the documentation as a reference when you have a problem it is frustrating to chase through a few links to get the "real" documentation.
Is that the idea, Guillaume? Jay 2011/7/6 Matthias Felleisen <matth...@ccs.neu.edu>: > > > Why is it pedagogical to repeat information in the > ISL documentation that the BSL documentation already > presented? > > -- Matthias > > > > > > On Jul 6, 2011, at 9:36 AM, Guillaume Marceau wrote: > >> On Wed, Jul 6, 2011 at 9:14 AM, Matthew Flatt <mfl...@cs.utah.edu> wrote: >>> In the case of the HtDP languages, was the choice to duplicate all the >>> text deliberate, or was it a side-effect of some other change? >> >> Yes, this was a deliberate move away from the no-duplication style >> used in the professional documentation, for pedagogical reasons. >> >> At each language level, I gathered in a separate section called >> "Common Syntax" the forms that that level has in common with the >> previous level. The idea is to make it possible to get a quick sense >> of of the commonality between the levels, while giving the students >> confidence that documentation page they are looking at is >> comprehensive. >> _________________________________________________ >> For list-related administrative tasks: >> http://lists.racket-lang.org/listinfo/dev > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev > -- Jay McCarthy <j...@cs.byu.edu> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev