Open GoogleCodeExporter opened 8 years ago
Original comment by pedag...@gmail.com
on 11 Aug 2010 at 6:55
As a first step, I think your first suggestion is a good one: it would be
fairly cheap to define a single file for all the tracing commands and provide
flags to switch them on or off at compile time. We can always add unsafe magic
later, but since one can usually just redirect stderr to a file, I wouldn't
prioritise it.
Would lhs2TeX formatting directives let us delete "proofTrace s" automatically,
when building the Epitome?
Original comment by adamgundry
on 12 Aug 2010 at 7:41
I have done the cheap thing and moved the tracing commands to a single file,
Kit/Trace.lhs. Feel free to experiment with hiding them.
Original comment by adamgundry
on 18 Aug 2010 at 4:08
Original issue reported on code.google.com by
pedag...@gmail.com
on 11 Aug 2010 at 6:39