This is not meant to be snide or flippant. Go actually made me learn Printf based debugging, and I am a much better debugger for it.
Add fmt.Printf() to your code. Or use a shortcut function like PP(), which will automatically show where it was called from to. I use a file like vprint.go in all my projects: https://github.com/gijit/gi/blob/master/pkg/verb/vprint.go#L22 You'll thank me when you get to multiple go routines. Printf restores sanity to debugging, and a debugger is mostly useless. It turns out the Printf yields a much faster debugging process too. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
