On Thu, Aug 19, 2010 at 7:56 AM, Shriram Krishnamurthi <[email protected]> wrote: > Neither would the PLT Web server. I'm pretty certain Jay's own edits > to it were not preceded by tests.
That's not true. > > Jay's changes to the PLAI language most certainly were not, because > the current PLAI that is bundled with DrRacket is broken. The thing that you are referring to was not tested, but I wrote a test suite for almost everything else. IMHO The problem with PLAI was that the printing was not part of the "spec". > > (Sorry, Jay, but it's your prose.) > > Shriram > > On Thu, Aug 19, 2010 at 9:50 AM, Casey Klein > <[email protected]> wrote: >> On Thu, Aug 19, 2010 at 8:44 AM, Sam Tobin-Hochstadt <[email protected]> >> wrote: >>> On Tue, Aug 17, 2010 at 3:57 PM, Jay McCarthy <[email protected]> >>> wrote: >>>> Please comment. >>> >>> I think that this: >>> >>> "Your first task when changing old code is to build an adequate test >>> suite to ensure you do not introduce new mistakes as you attempt to >>> improve it. Thank you for improving the world for future generations!" >>> >>> is too demanding. There are enormous areas of our code that don't >>> have a test suite. How comprehensive a test suite do I need before >>> changing slideshow? Or scribble (which has a test suite for the >>> syntax, but not the language)? >> >> Robby and Matthew, would Slideshow exist today if you'd be expected to >> build it with this process? >> _________________________________________________ >> 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 <[email protected]> Assistant Professor / Brigham Young University http://teammccarthy.org/jay "The glory of God is Intelligence" - D&C 93 _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
