compiler-warnings

I have a function pointer inside a struct that gets dynamically set at runtime to the address of another function in various places in my code. It is defined in my header file like this: void *(*run)(); During compile time, I get the following warning about this: warning: function declaration isn't a prototype This warning is benign, because the pointer is used in many places in my code to call the function it points to, and everything works just fine. However, I would really like to silence the warning. If I change it to this: void *(*run)(void); I get compile errors whever I use it, because

Does anyone know a gcc/g++ option that generates an error/warning if there's a function that has a non-void return value but doesn't contain a return statement in its definition? e.g.: int add(int a, int b) { a+b; } Many thanks in advance! -Wreturn-type . It's enabled by -Wall (which you should always be running with, along with -Werror -Wextra ). 来源： https://stackoverflow.com/questions/9924570/gcc-options-warning-on-non-void-functions-without-a-return-statement

I'm wondering why I am getting an warning about initialization in one case, but not the other. The code is in a C++ source file, and using GCC 4.7 with -std=c++11 . struct sigaction old_handler, new_handler; The above produces NO warnings with -Wall and -Wextra . struct sigaction old_handler={}, new_handler={}; struct sigaction old_handler={0}, new_handler={0}; The above produces warnings: warning: missing initializer for member ‘sigaction::__sigaction_handler’ [-Wmissing-field-initializers] warning: missing initializer for member ‘sigaction::sa_mask’ [-Wmissing-field-initializers] warning:

Consider this: id observer = [[NSNotificationCenter defaultCenter] addObserverForName:MyNotification object:nil queue:nil usingBlock:^(NSNotification *note) { [[NSNotificationCenter defaultCenter] removeObserver:observer name:MyNotification object:nil ]; // do other stuff here... } ]; I'm using this pattern to observe a notification once and then stop observing it. But LLVM tells me (under ARC) that Variable 'observer' is uninitialized when captured by block. How can I fix this, since the block necessarily captures the variable before initialization, it being part of the initializer? Will

In my project's settings in Visual Studio, I have set 'Treat warnings as errors' to 'All'. The Warning level is set to 4. I tested this by deliberately introducing code that violates CA1305, but it builds (and rebuilds) successfully, returning a Warning. What I expected was that the build would fail and an Error would be returned. Is my understanding wrong? Code Analysis uses a different mechanism to treat warnings as errors. To have Code Analysis warnings treated as such, add a new Code Analysis Ruleset to your solution. To do so, rightclick your solution and choose "Add new item...". Search

I am attempting to implement function overloading in C , and I am very close. I am using C99 so the _Generic keyword introduced in C11 is not available to me. I have developed some working code, but when I compile it I get a couple warnings. Working example: #include <stdio.h> #define print(x) \ __builtin_choose_expr(__builtin_types_compatible_p(typeof(x), int ), print_int(x) , \ __builtin_choose_expr(__builtin_types_compatible_p(typeof(x), char[]), print_string(x), \ (void)0)) void print_int(int i) { printf("int: %d\n", i); } void print_string(char* s) { printf("char*: %s\n", s); } int main