Quote:
|
As for your other complaints -- I hear ya brother. Gotta love C++.
|
Indeed. What do you guys mostly code in?
Thank you, Matt! With those pointers in the right direction (heh), I think I understand the code now.
So, just to recap:
-START_ROBOT_CLASS, through many convolutions, defines the entry point FRC_UserProgram_StartupLibraryInit, which is called from external code (on the cRIO), which:
-Spawns a new task running an instance of the robot class
Do I have that right?
OK, so, in lieu of using try-catch blocks, I should use wpi_assert around conditionals that try to trap errors like null pointers? From what I can tell, this prints a message to the console (and puts a condition on the stack?). So, if I wanted to flush the error stack, I'd use wpi_assertCleanStatus.
What's the difference between wpi_assert and wpi_fatal?