How do I get rid of the "deprecated conversion" warning in CDT? I know how to #pragma it out of the compilation process but the highlighting in the CDT is annoying!
The warning, more probably than not, comes from the compiler. If you compiled and got the warning and later on removed it from the compilation process by means of a pragma or compiler option, it might be the case that the IDE still remembers it. It should go away in a later compilation, or you can manually delete within the Problems windows.
If you have not removed it from the compilation process (that is, the warning comes out in each new compilation) this will be mainly useless as the warning will come back. But then again, if it is still there, the IDE is just reminding you.
Related
I would like to take a step backwards opening eclipse without it automatically opening the source files which were last open, nor the projects which were last loaded, I have reason to believe this might clear it all up.
Motivation being that as of a forced quit of eclipse, after it had gone stuck after some project changes, my eclipse Luna is no longer able to start without getting hung up again.
How may I accomplish that?
It's important to me not to lose my settings such as syntax highlighting and stuff, while performing the salvation... and whereas I am pretty certain I could locate my workspace directory on disk, would be nice finding where does eclipse keep the pointer to it, just to make sure I'll be tinkering with the right workspace, if needed..
I guess I could call it "starting eclipse in safe mode" :)
So, I am developing with eclipse 4.2 and groovy 2.3 / jdk 1.6.0_35.
I just worked on one of my classes when suddenly eclipse showed me a dozen compile errors in different classes out of nowhere. It says e.g. it can't find a class in an import statement, although the class is there. Running the code works fine even though the errors are shown. If I add a comment to one of the classes and save it, some errors go away but may come back as soon as I change another (totally different) class.
It also shows me some errors like these:
error description:
As you see, the error is totally unrelated (Optional is totally independent of any other class, also of course independend of the mentioned classes in the error message). If I add a comment somewhere and save Optional, the error goes away but comes back as soon as I save any other class.
I cleaned the project, deleted the bin-directory and restarted eclipse/computer but it didnt' help. Does anyone already experienced this behaviour? How to fix it?
I got similar problem and error was in file above one with compilation error. So try to comment file before and check if this solve problem.
I am new to Netbeans. Netbeans shows an error as below:
But the error text is: incompatible types: List cannot be converted to Vertex. I'm sure it's referring to the code below it that uses Vertex in many places, but the file is long and I have no idea which line to go to. Is there a way to fix this, or is this a bug, or am I interpreting everything wrongly?
Bug still there, but a workaround is to run the project and the compile error will show up in the output. I'm used to Eclipse where you normally can't run a project with complier errors. But this is a way to find the line.
I have a little problem.
I just installed Eclipse CDT and created a C project using MinGW and all my simple warnings (like "unused variable" etc) are shown as errors.
The program build fine and I can run it, but all these errors are annoying.
I already checked the compiler settings and "Warnings as errors (-Werror)" is unchecked.
What do i do?
In my case, the problem was caused because the compiler/builder's message was in a different language than Eclipse.
Thus, Eclipse could not identify them as Warnings and thought they were Errors instead.
I solved by making an environment variable to set the compiler to the right language,
Thanks to this question
As the messages were sent on the right language, Eclipse changed the markers to warnings and compiled without any error messages.
If -Werror would be checked, the build would fail. By the way you should definitely check it so that it enforces you to take care of all the warnings right from the beginning.
You can suppress some warnings (but not all), with special options to GCC (MinGW). You can see which options are needed to suppress this or that warning in the end of the warning itself.
Nevertheless, I strongly recommend against it. It's rather better to resolve all the warnings right from the beginning. Strive to design your projects in the way that they are able to be built with -pedantic -Wall -Wextra -Werror options. There are 3 main benefits of this approach:
Your code would be nearly bulletproof;
Your code would conform to the standard closely;
Your code would be more portable across different compilers
(as some of them tend to treat some warnings as errors by default).
Remember, leaving the annoying warning flood is a bad habit, and you should definitely get rid of it right from the start.
I just updated to the latest Scala-IDE version on Eclipse, and it's highlighting loads of spurious "illegal cyclic inheritance" errors in code I know to be OK (it was before, and it still compiles and runs OK).
Any way to fix this? If not, how do I roll back to the previous version? I don't see any options to roll back or download earlier versions on the Scala IDE website.
Thanks.
edit: Never mind, it spontaneously sorted itself out after about 10 minutes sitting there showing errors. Will leave question here in case else anyone gets this.
"Project -> Clean Project" always helps me when Scala-IDE is showing weird error messages.
Sometimes errors will show in the editor, but not in the package explorer. Things still appear to compile ok when that occurs.