Brecht Geeraerts wrote:A good way is also to try and read your code.
For me that would be my last choice. If I didn't have access to a Java compiler and somebody demanded for me to do that, then I would reluctantly do it. But that code has features which seem to be designed to have off-by-one errors which I would have to think hard about. And why think hard when you can just run the code and see what it does? Programmers should be lazy, after all.
It runs on an internal combustion engine. This ad does not:
Devious Experiments for a Truly Passive Greenhouse!