From: <no...@so...> - 2001-03-24 02:14:24
|
Patches item #403189, was updated on 2001-01-11 01:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=310894&aid=403189&group_id=10894 Category: interp Command Group: None Status: Open Priority: 5 Submitted By: Mo DeJong (mdejong) >Assigned to: Mo DeJong (mdejong) Summary: A couple of interp.test improvements Initial Comment: I found a pwd problem in Jacl while running some interp related tests, it seems that there are no test in interp.test that check to see if a child interp inherits the parent's current working directory. I added a new test to interp.test to cover that case. I also noticed a spot where no warning was printed if a test* command did not exist. In addition, I added a echo statement to the "make runtest" rule that will make it easy to get to the test dir when build dir != src dir. ---------------------------------------------------------------------- >Comment By: Jeffrey Hobbs (hobbs) Date: 2001-03-23 18:14 Message: Logged In: YES user_id=72656 We should go ahead with this patch. As for there not being a test for this before, that's because all Tcl's interp share the cwd by OS design. Of course, no harm in testing that. ---------------------------------------------------------------------- Comment By: Mo DeJong (mdejong) Date: 2001-01-16 13:13 Message: The tests depend on the current directory on the user's system, so I would not be possible to return a known path. Someone would need to run the test case and examine the results by hand if it failed. The "command xyz is not defined" warning messages are all over the Tcl test suite, so that should not be an issue. Sure it might be nice to di it with constraints, but that would mean rewriting lots of tests. I am not sure what you mean about the echoed message. This would only happen when the user ran "make runtest", which is the method you would use to enter the interactive version of "make test". The problem is that you don't know where the $srcdir is but you need to cd to $srddir/tests before you can start sourcing test files. ---------------------------------------------------------------------- Comment By: Donal K. Fellows (dkf) Date: 2001-01-16 03:34 Message: I see no reason to not support the addition of the cd/interp test, though you may want to change it a little so that if the test fails, a more informative error message gets spat out by the test harness. On the warning message, I'm not too sure that any part of the test suite should print up warning messages except for due a test failure. Doing some kind of fiddling around with constraints (so the existence of certain commands could be turned into a constraint that is not met) would be better, since the presence or absence of a command is really a constraining factor, and skips due to constraint failure get a nice message at the end. The echoed message just looks a little confusing to me; remember that we are running in a shell-domain here, so random bits of echoed Tcl will confuse as likely as not. Update it so that it makes sense from either point of view (i.e. by adding additional text) and I'll be much happier. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=310894&aid=403189&group_id=10894 |