[m-dev.] diff: Re-enable DD test cases
Mark Anthony BROWN
dougl at cs.mu.OZ.AU
Thu Jan 6 18:06:58 AEDT 2000
Zoltan Somogyi writes:
>
>
> > --- tests/debugger/declarative/app.exp 2000/01/03 02:22:51 1.2
> > +++ tests/debugger/declarative/app.exp 2000/01/05 17:02:12
> > @@ -3,7 +3,7 @@
> > Command echo enabled.
> > mdb> break app
> > Registering debuggable procedures... done.
> > -There is one debuggable module, with 5 procedures.
> > +There are 67 debuggable modules, with a total of 3206 procedures.
>
> Where do the other 66 modules come from? Some from the browser and some
> from the standard library, but I didn't think you needed to pull in *all*
> the standard library modules.
The tests can be run in grades with or without debugging, so there is
one set of expected output files for each case. If there is a difference,
then the *.res files are generated from the *.exp2 files, so I have made
the *.exp files be for debug grades, and the *.exp2 files be for
non-debug grades (which the tests would be run in more often, I expect).
That way, the *.res files usually wind up smaller. The log message
probably could have been clearer, I guess.
(Perhaps I have misunderstood your point?)
> In any case, this sort of expected output becomes out of date quite quickly.
> This is exactly why I added the "register --quiet" command. You should issue
> it in the .inp script before any "break" commands.
>
Good idea. I'll add it shortly.
> Apart from that, and the quick and dirty output format, the diff is OK.
>
On a side note, I have been experimenting with a "portray" mechanism
which will allow users to declare their types as being instances
of a `portrayable' typeclass. It still needs more work, but I hope
to be able to use this to clean up the output (and I hope it to be of
more general use, of course). But I'll save discussion of this for
another thread...
Cheers,
Mark
--
Mark Brown, PhD student )O+ | "Another of Fortran's breakthroughs
(m.brown at cs.mu.oz.au) | was the GOTO statement, which was...
Dept. of Computer Science and Software | uniquely simple and understandable"
Engineering, University of Melbourne | -- IEEE, 1994
--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to: mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions: mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------
More information about the developers
mailing list