Exception being thrown by challenges
Closed this issue · 3 comments
I don't think challenges should be throwing an exception if they use invalid Instructions, it should be a boolean or something instead.
Also it is slightly frustrating not being able to test my own code, because it doesn't conform to the challenge.
Sorry about that; that's what FreeDesignMode is for.
You could switch to it when the ApplicationFrame starts up.
Still need to implement graphical switching.
On Thursday, 2 May 2013 at 13:36, greglo wrote:
I don't think challenges should be throwing an exception if they use invalid Instructions, it should be a boolean or something instead.
Also it is slightly frustrating not being able to test my own code, because it doesn't conform to the challenge.—
Reply to this email directly or view it on GitHub (#22).
There are two different issues being conflated here: exceptions are being thrown even in FreeDesignMode, which is a (easy-to-fix) bug, and I've opened a separate issue for it. There's also the question of how to handle people using an invalid instruction set; my thinking is that this should be dealt with by the Check Code stuff and handled gracefully there.
I'm about to push a commit changing the initial mode to FreeDesignMode, and once the bug in the other issue is fixed we shouldn't have any more problems.
Currently displays an error, but doesn't stop the user continuing.