title: how bad is it to use dynamic datastuctures on an embedded system?
body: <p>So in an embedded systems unit, that i'm taking at uni next year, we will learn that dynamic data structures are a bad thing to have in an embedded system program.
  but the lecture notes don't go into why.</p>
  
  <p>Now i'm working on a moderate scale, embedded systems\ 'LURC' controller, mostly just takes advantages of the peripheral of the "Butterfly" demo board for the AVR169MEGA.
  produced 4 PWM signals to contol servo's and ESC. and also to provide an 9 seg LCD screen.</p>
  
  <p>Now I can't think of anybetter way to store instructions as they are recieved vial USART serial, than a queue.
  esp for things where I'll need to wait until an unknown amount of data has been recieved: eg a string to display on the LCD screen.</p>
  
  <p>so why don't you uses dynamic data structures on a microcontroller in a embedded systems?
  Is it just that you're on a heavily memory restricted enviroment, and have to be sure your mallocs are succeeding?</p>