Quote:
Originally Posted by jlindquist74
I strongly discourage our programming team from making any calls that might communicate with hardware in their constructors. To do so assumes that the "under the covers" initialization done by WPILib is complete and the hardware can be reached at the time the constructor executes.
|
I agree. In this case, I was actually more worried about the EnableControl() call than the SetSafetyEnabled() call, but figured it was outside the scope of this question. You raise a good point, though.