compiler-warnings

I was trying to answer this question. As suggested by the accepted answer, the problem with that code is that not all control paths are returning a value. I tried this code on the VC9 compiler and it gave me a warning about the same. My question is why is just a warning and not an error? Also, in case the path which doesn't return a value gets executed, what will be returned by the function (It has to return something) ? Is it just whatever is there on top of the stack or is the dreaded undefined behavior again? Failing to return a value from a function that has a non- void return type results

I have a simple C++ with Boost like this: #include <boost/algorithm/string.hpp> int main() { std::string latlonStr = "hello,ergr()()rg(rg)"; boost::find_format_all(latlonStr,boost::token_finder(boost::is_any_of("(,)")),boost::const_formatter(" ")); This works fine; it replaces every occurrence of ( ) , with a " " However, I get this warning when compiling: I'm using MSVC 2008, Boost 1.37.0. 1>Compiling... 1>mainTest.cpp 1>c:\work\minescout-feat-000\extlib\boost\algorithm\string\detail\classification.hpp(102) : warning C4996: 'std::copy': Function call with parameters that may be unsafe - this

I was writing some code today and got a weird compile error, which seems to be caused by initializing member variables in a different order than they were declared. Example: class Test { int a; int b; public: Test() : b(1), a(2) { } }; int main() { Test test; return 0; } Then if I compile it with -Werror -Wall : $ g++ -Werror -Wall test.cpp test.cpp: In constructor ‘Test::Test()’: test.cpp:3:9: error: ‘Test::b’ will be initialized after [-Werror=reorder] test.cpp:2:9: error: ‘int Test::a’ [-Werror=reorder] test.cpp:6:5: error: when initialized here [-Werror=reorder] cc1plus: all warnings being

There are some files in my iOS project that have some warnings, and I want to ignore those warnings. I don't want to disable warnings in the entire project (know how to do that), just some specific files. So, is there a way to completely ignore all warnings from a specific file? I'm using LLVM 3.0 and Clang on Xcode 4.2. if you're just using clang, then you should use the pragma syntax for sources you maintain (assuming it is impossible to remove the warning by altering the program appropriately). here is the syntax: #pragma clang diagnostic push #pragma clang diagnostic ignored "-Wmultichar"

Why do the following lines of code not create a compiler warning? void Main() { throw new Exception(); throw new Exception(); } As I see it, the compiler should inform you that the second throw exception cannot be reached. It is clearly a compiler bug, and it was introduced in C# 3.0 -- right around the time that I heavily refactored the reachability checker. This is probably my bad, sorry. The bug is completely benign; basically, we just forgot a case in the warning reporter. We generate the reachability information correctly; as others have noted, we correctly trim out the unreachable code