Neil Jerram <[EMAIL PROTECTED]> writes: > > (define coverage-trap (make <entry-trap> #:behaviour cover-entry))
You don't have to use goops to get a trap do you? > guile-statprof does a better job of trying to mitigate the > latter factor, so is in fact a better current bet for profiling Guile > code. I expect there's a place for both extry/exit and prof style. _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://lists.gnu.org/mailman/listinfo/guile-devel
