|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
pic: Totally Desctiptive Object Name
|
|
#2
|
|||||
|
|||||
|
Re: pic: Totally Desctiptive Object Name
Every robot needs a locky-thingy. A robot without one might fire when it isn't supposed to, and hit the wrong target; e.g., a referee, FTA, or robot inspector.
Wouldn't want that. Better put in the locky-thingy. |
|
#3
|
||||
|
||||
|
Re: pic: Totally Desctiptive Object Name
When I first read the title, I thought it said 'deceptive object name' at which point it could be named "THE_unlock".
|
|
#4
|
||||
|
||||
|
Re: pic: Totally Desctiptive Object Name
Quote:
But since in this picture, the project is called DrawingPad, I'm assuming this isn't for an FRC bot. Last edited by cjl2625 : 30-10-2014 at 09:54. |
|
#5
|
||||
|
||||
|
Re: pic: Totally Desctiptive Object Name
It's actually a mutex, so it is supposed to lock data during reads and rights. Without properly using it, the software would crash spectacularly as the server is 100% threaded! Memory does not like to be read and written to at the same time, at the same location.
|
|
#6
|
|||||
|
|||||
|
Re: pic: Totally Desctiptive Object Name
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|