On Saturday, 19 December 2015 17:24:01 UTC-5, Matthias Felleisen wrote: [...] Hi Matthias,
Thanks for that quick and informative reply. We've been teaching a breadth course (at University of Toronto) that has always had a taste of programming, but in recent years with the help of DrRacket and the *SL languages, and the strong interest of the non-technical audience, has steadily evolved from containing a "taste" of programming to being at the edge of program design. This term the increment put it over an edge where not doing a full design process, and not covering how to fully notice and interpret the results of errors, was a major source of difficulty. It was exacerbated by some creative approaches students had to tackling implementation of a program with many given check-expects to fulfill: they sometimes copied and pasted, or typed in incrementally, parts of the starter file from the view of it in their browser. They also commented out or re-arranged parts of the file, or deleted parts (sometimes accidentally, sometimes because they got confused about which parts they had added). We'll accept your experience and hopefully now that we understand the behaviour of check-expect, and of the students, we can address that in the course. I'll probably have more comments about other things that we find tripping us up, and say in advance that we are very grateful for everyone's work on racket, and it's so good in so many ways that it makes us want more. As a quick question on the current topic: except for a note in htdp2e about check-expects being gathered and evaluated at the end of the program, is the information about its behaviour on errors mentioned somewhere? -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
