Thread: Timing, threads, the Field Management System, etc
View Single Post
  #7   Spotlight this post!  
Unread 13-03-2016, 23:59
jkoritzinsky jkoritzinsky is offline
Registered User
AKA: Jeremy Koritzinsky
FRC #4786 (Nicolet F.E.A.R.)
Team Role: Mentor
  
Join Date: Apr 2014
Rookie Year: 2014
Location: Glendale, Wisconsin
Posts: 78
jkoritzinsky will become famous soon enoughjkoritzinsky will become famous soon enough
Re: Timing, threads, the Field Management System, etc
Quote:
Originally Posted by virtuald View Post
Threads are also evil (once again, with exceptions) in robot code and when used improperly can lead to difficult to diagnose bugs, prefer asynchronous constructs such as state machines instead.
Threads are always evil. Way too easy to put yourself into a deadlock/livelock or put your code in an "impossible" situation with bad use of concurrency constructs. Really the problem is mutable state + threading + bad use of concurrency constructs.
__________________
Nicolet F.E.A.R. (Team 4786) - Aerial Assist - Programming Manager
Nicolet F.E.A.R. (Team 4786) - 2015+ - Junior Mentor

SuperScouter for FRC Developer