Quote:
Originally Posted by Kevin Watson
Just out of curiousity, are you referring to my code or IFI's? If it's my code, what can be done better?
-Kevin
|
It wasn't a criticism of any code. I couldn't criticize any code, because I can't tell what it is doing. It looks to me like a shell that is filled with functions that I should code. Unfortunately, I don't really know what to do with them, and even if I did, being a mentor for a rookie team, we don't have a robot to download to and most likely won't have one for a while.
I have borrowed a Vex robot, and I have ordered parts to build my own small toy robot, just to have a chance to work on the software. One of the kids is going to put the Vex robot together in the next few days.
Specifically, I don't understand how the software system is supposed to work. Apparently I missed out on the thorough documentation that Mr. Anderson has alluded to, but I might have it now, I hope.
The EasyC system (which we did not really look at) seems to be well documented and has explanations of how you do things. I can program in C, so I didn't look at it, as I usually find code generators to be tedious, limited, and just basically in the way.
I'm sure that once I can actually download the code into a robot and experiment, it will all make sense.