View Single Post
  #2   Spotlight this post!  
Unread 13-01-2015, 18:41
alopex_rex's Avatar
alopex_rex alopex_rex is offline
Rainbow Professionalism Dash
AKA: Scott Morton
FRC #0830 (The RatPack)
Team Role: Alumni
 
Join Date: Dec 2014
Rookie Year: 2012
Location: Ann Arbor, MI
Posts: 92
alopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond reputealopex_rex has a reputation beyond repute
Re: UINTs not working?

We noticed this too when we copied in an old gamepad utility class. UINT32 and its ilk are not built-in C++ types; they're part of WPILib. If you dug around you might be able to find a file with "typedef UINT32 unsigned int" or something like that. As best I can tell, WPILib no longer uses the "UINT32" style of names for these types. Now they write them like "uint32_t", which is more typical style for naming custom types.

Technically speaking, C++ types such as "int" do not correspond to a specified amount of memory, although in practice int is always 32-bit. The WPILib people want a more a clear/unambiguous system, so they define their own type names, like UINT32 or uint32_t instead of "unsigned int".

There's no reason to use that in your code though; just replace all your UINT's with int or unsigned int. ctrl-f followed by "replace all" is how we did it.
__________________
Ratpack programming lead 2013 - 2015

ἔκλαγξαν δ᾽ ἄρ᾽ ὀϊστοὶ ἐπ᾽ ὤμων χωομένοιο / αὐτοῦ κινηθέντος: ὃ δ᾽ ἤϊε νυκτὶ ἐοικώς. (Ancient Greek nerds unite!)

Last edited by alopex_rex : 13-01-2015 at 18:50. Reason: edited for clarity