If I do pretty_print(m1,profiler). pretty_print(m2,profiler). each time this is called the numbers inserted into the transformed code start from 1 again. I think that's OK. But if I call pretty_print([m1,m2],profiler) (an undocumented feature I know) I would expect the count not to be reset, so I would get a correct report when running pretty_print([m1,m2],coverage). The result of having the count reset is that all the profiles in the different files show the same values. This is the last one because I am giving up on this feature for now. btw I think the generic way to use the coverage tool is % Modules is a list of modules that implement my app coverage_test(Modules,TestCall) :- pretty_print(Modules,profiler), cd(profiler), compile(Modules), % replaces all the un-transformed modules you will have compiled beforehand. cd('..'), call(TestCall), pretty_print(Modules,coverage). Stefano 2nd Floor The Tower Building EMAIL: Stefano.Novello@parc-technologies.com 11 York Road TEL: +44 20 72614017 SE1 7NX LONDON FAX: +44 20 72614001 This e-mail message is for the sole use of the intended recipient(s) - its contents are the property of Parc Technologies Limited (or its licensors) and are confidential. Please do not copy, review, use (except for the intended purposes), disclose or distribute the e-mail or its contents or allow anyone else to do so without our prior permission. Parc Technologies Limited does not guarantee that this e-mail has not been intercepted and amended nor that it is virus-free. You should carry out your own virus checks before opening any attachment. Any opinions expressed in this e-mail message are those of the author and not necessarily Parc Technologies Limited. Limited.Received on Tue Jul 10 20:39:24 2001
This archive was generated by hypermail 2.1.8 : Wed 16 Nov 2005 06:08:08 PM GMT GMT