Quote:
Originally Posted by blakeelias
That's awesome! I was looking for a way to automatically make a dummy library, but I couldn't find anything that would simulate the interactions between all the classes. It looks like yours catches any syntax errors and even some runtime errors -- better than a local compiler!
|
Yeah, my intent was to use it sorta like a compiler, so we wouldn't have to worry so much about runtime errors. But -- it's not automatically generated by anything, we created the harness and classes by writing the code ourselves. But once it was implemented, it was really easy to add new things to it, and was a great little set of tests.
Quote:
Originally Posted by blakeelias
You also hacked winpdb to run on the cRIO, right? How did that work out?
|
Well, it worked, though we ended up not needing to use it particularly often at all. For python I've just been finding it easier to use print statements to debug things. Once or twice I've used winpdb... but, our code isn't particularly complex, so print() works just fine
