Ask Your Question

Revision history [back]

Well, debugging will be laborious I think. But instead of print statements I think verbose is at least a little easier.

  • First, it automatically prints the name of the function it's embedded in; you can narrow in on the bug pretty quickly by just putting verbose('working..') in some key places (of course, something even more informative would be better).
  • Second, it's off by default -- you turn it on with set_verbose(n). So you can insert a bunch of verbose statements instead of print statements, turn verbose on to see what's happening, and then turn it back off when you don't want to see anymore.

There's also some "level" functionality, which I don't quite understand but has to do with function calls within function calls within ... The purpose, I guess, is to avoid being overloaded with the verbose output of sub sub sub routines.