30-10-2014 05:56

Richard Wallace

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.

30-10-2014 09:30

JesseK

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".

30-10-2014 09:49

cjl2625

Re: pic: Totally Desctiptive Object Name

Quote:

Originally Posted by Richard Wallace 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.

30-10-2014 14:03

yash101

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.

02-11-2014 17:18

DonRotolo

Re: pic: Totally Desctiptive Object Name

Quote:

Originally Posted by yash101 Memory does not like to be read and written to at the same time, at the same location.