title: Turn off eclipse errors (that aren't really errors)
body: <blockquote>
    <p><strong>Possible Duplicate:</strong><br>
    <a href="https://stackoverflow.com/questions/13458396/disable-eclipses-error-discovery-c11-false-positives">Disable Eclipse&#39;s error discovery. (Codan false positives)</a>  </p>
  </blockquote>
  
  
  
  <p>With GCC 4.8/Clang 3.3 C++ support so far ahead of what Eclipse is doing with syntax checking (in terms of feature support), Eclipse is marking many things as errors that are actually valid code (template aliasing happens to be my main problem, but there are other issues as well).</p>
  
  <p>When I compile (or attempt to anyway, having some issues, see <a href="https://stackoverflow.com/questions/14118224/clang-linker-issues-from-source-to-gcc-snapshot">here</a> for more) whatever compiler happens to be doing the work does its job, and its errors get propagated through, but the code that it says is OK is still underlines (red and gold spiders for errors and warnings respectively), which makes it much harder to see what is going on.</p>
  
  <p>Is there a way to get rid of these errors/warnings?</p>
  
  <p>Even better would be a way to get rid of warnings only after compile attempt, and for as long as the relevant parts of the code don't change, but still leave them enabled in general.</p>
  
  <p>(Actually the best would be a plugin for Eclipse that supports all, or at least more of C++11 than Juno does by itself, but I can't seem to find that)</p>