View Single Post
  #1   Spotlight this post!  
Unread 26-11-2011, 21:48
Ginto8's Avatar
Ginto8 Ginto8 is offline
Programming Lead
AKA: Joe Doyle
FRC #2729 (Storm)
Team Role: Programmer
 
Join Date: Oct 2010
Rookie Year: 2010
Location: Marlton, NJ
Posts: 174
Ginto8 is a glorious beacon of lightGinto8 is a glorious beacon of lightGinto8 is a glorious beacon of lightGinto8 is a glorious beacon of lightGinto8 is a glorious beacon of light
Question Dummy WPILibJ: "parsing" package?

Hey guys, I've been working on a handy little software testing tool that lets you test code (at least to a certain extent) without having to download to the robot. My method for this involves creating a sort of dummy version for WPILibJ with an added Swing application that lets you modify different inputs, such as joystick axis positions and sensor values, and observe the output values, primarily motor speeds and servo positions. It will hopefully help tremendously with initial code testing, although tweaking in order to get it to work correctly with the hardware will still be necessary.

So onto my (sorta) problem. I've been trying to really understand some of the connections between the different parts of WPILibJ, and most are pretty logical. However, there is one part which has so far escaped my grasp: the parsing package. All it contains is a group of 6 blank interfaces, which are implemented by a number of classes within the library. So my question is: what are they for? Are they used by the VM for some purpose, or are they just a simple way to classify different parts of the library? I ask because if there's something special done by the VM, I want to make sure I account for it in my dummy library.
Reply With Quote