title: What specifically are the dangers of eval(parse(...))?
body: <p>There are several questions on how to avoid using <code>eval(parse(...))</code></p>
  
  <ul>
  <li><a href="https://stackoverflow.com/questions/11025031/r-evalparse-is-often-suboptimal">r-evalparse-is-often-suboptimal</a></li>
  <li><a href="https://stackoverflow.com/questions/13647046/avoiding-the-infamous-evalparse-construct">avoiding-the-infamous-evalparse-construct</a></li>
  </ul>
  
  <p>Which sparks the questions:</p>
  
  <ul>
  <li>Why Specifically should <code>eval(parse())</code> be avoided?  </li>
  <li>And most importantly, What are the dangers? 
  
  <ul>
  <li>Are there any dangerous if the code is not used in production? (I'm thinking, any danger of getting back unintended results. Clearly if you are not careful about what you are parsing, you will have issues. But is that any more dangerous than being sloppy with <code>get()</code>?) </li>
  </ul></li>
  </ul>