What would happen if we threw it out now (on the trunk, not on the release branch)?
Robby On Tue, Mar 17, 2009 at 9:52 AM, Matthias Felleisen <[email protected]> wrote: > > On Mar 17, 2009, at 10:16 AM, Kathryn Gray wrote: > >> >> On 17 Mar 2009, at 1:53:33, Matthias Felleisen wrote: >> >>> >>> On Mar 17, 2009, at 8:58 AM, Kathryn Gray wrote: >>> >>>> The test-engine/scheme-tests.ss can be used as a library by programs >>>> that aren't written in the teaching language currently; the test results >>>> from this library appear in print statements instead of a window in >>>> DrScheme. >>> >>> So does htdp/testing ... (test) . Why are we deprecating htdp/testing >>> again? >> >> >> The functionality doesn't need to (and isn't) going away. >> >> All htdp/testing does is reexport items from the other library, but unlike >> test-engine/scheme-tests it can easily be added by students as a teach pack. >> >> If a student does this, and then calls (test) manually; all of their test >> results appear twice. Why is this a desirable behavior to have? Why should >> we be letting students add this as a teach pack? > > > I remembered that it was a re-export of functionality. I had forgotten about > the testing-twice part. > > Let's print "deprecated, require test-engine/scheme-tests" instead from > htdp/testing. And by 5.0 we throw it out. > > Thanks -- Matthias > > _________________________________________________ > For list-related administrative tasks: > http://list.cs.brown.edu/mailman/listinfo/plt-dev > _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
