Thread: Programming languages in the embedded enviroment
View Single Post
  #9   Spotlight this post!  
Unread 05-01-2008, 09:10
Astronouth7303's Avatar
Astronouth7303 Astronouth7303 is offline
Why did I come back?
AKA: Jamie Bliss
FRC #4967 (That ONE Team)
Team Role: Mentor
  
Join Date: Jan 2004
Rookie Year: 2004
Location: Grand Rapids, MI
Posts: 2,071
Astronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud ofAstronouth7303 has much to be proud of
Re: Programming languages in the embedded enviroment
For what FIRSTers do, C is fine. As soon as you remove pointers & dynamic memory, C and Python become essentially equivalent.

Where interpreted languages shine is when you use things like objects/classes, dynamic memory, etc. It's hard enough to debug a memleak on a PC, much less on an embedded system.

When many teams struggle with programming at all, keeping programming simple should be a priority. Be it Python, C, Ruby, Perl, or another language, make easy to pick up.

The point of FIRST is to not train students for the workforce. FIRST does not replace school. No matter what language you use, some fundamental concepts (eg sensor feedback, control loops, autonomous programming) still apply.