|Re: Symbol could not be resolved errors [message #1137559 is a reply to message #1137506]
||Mon, 14 October 2013 15:27
| Mike Tarullo
Registered: April 2010
Well after looking at similar post for this error on the forum I found a solution (or at least a workaround) for this problem.|
I found a post that talked about the errors coming from the static code checker. So I started poking around the preferences to see if there was a way to set the location of the include paths for the static checker. I did not find any (but I'll keep looking) but I did find a way to turn of the error, permanently! In Window -> Preferences -> C\C++ -> Code Analysis just uncheck all the error checking!
Now I know that static checking is a "somewhat" nice feature. But when the complier is going to do this anyway we must ask ourselves is it really needed? Is it worthwhile giving up machine cycles for something that is going to be checked again anyway? Not only do unnecessary feature bloat our code, when we add a feature that does not work, like appears to be the case here, what service do we provide to our users?
While I was looking at the forum for similar post for this error, I noticed many posts where developers were frustrated with Eclipse. I have used it for years and it can be a love\hate relationship. When it works it's great, when it does not it's frustrating, but that is true for just about anything (including Congress!).
So my suggestion to the Eclipse contributors is don't bloat the software, especially if the feature does not work! And my suggestion to the complainers is be a little more professional in your posts. Offer suggestions or constructive opinions and leave the f---ing out of your posts. It short, grow up!
Powered by FUDForum
. Page generated in 0.03419 seconds