View Single Post
  #5   Spotlight this post!  
Unread 18-02-2003, 17:44
Mike Soukup's Avatar
Mike Soukup Mike Soukup is offline
Software guy
FRC #0111 (Wildstang)
Team Role: Engineer
 
Join Date: May 2001
Rookie Year: 1996
Location: Schaumburg, IL
Posts: 797
Mike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond reputeMike Soukup has a reputation beyond repute
AFAIK the previous posters are correct, you cannot get the code from the RC and decompile it.

I hope everyone learns a lesson from this. Whenever you make significant changes to the code, back it up first. Either use version numbers in the file name or use the date. That way you can always go back to code that works and you can see what changes you made that may have broken the code. This is the method we've used in years past.

This year we're using version control software (CVS) instead of saving backup copies. We commit the code whenever we make significant progress and label it when we reach milestones. We can easily & quickly look through the file's history log and we can see the changes between any two versions. Experiment with CVS after the season and use it for next year's software. It's worth the initial learning curve. http://www.cvshome.org/