compiler-warnings

This question already has an answer here: Why is there not any warning on a declaration without initialization in a for loop? 1 answer Once again a stupid uninitialized variable error in How to fix this segmentation error in a sequence inverting program? . So I was going to repeat the "please use -Wall flags" comment, but when I tested the code against warnings, I found no warnings reported to my great surprise. So I trimmed it down to this below (this code makes no sense for execution purposes but it illustrates what I want to show): #include <stdio.h> int main() { int i,len=12; /* printf("%d

Anyone know how to solve this warning message? Ambiguity between method 'Microsoft.Office.Interop.Word._Document.Close(ref object, ref object, ref object)' and non-method 'Microsoft.Office.Interop.Word.DocumentEvents2_Event.Close'. Using method group. Tod The only way I've managed to resolve the warning is to use an explicit cast: var doc_close = (Microsoft.Office.Interop.Word._Document) _doc; doc_close.Close(); If you already have a using for Microsoft.Office.Interop.Word you can simplify the cast to: var doc_close = (_Document) _doc; doc_close.Close(); or even just ((_Document)_doc).Close();

I'm a Linux user who started learning C and I'm trying to compile this source that I typed: #include <stdio.h> main() { float c,d; c = 10215.3; d = c / 3; printf("%3.2f\n",d); return 0; } It compiled with this using a makefile that I wrote: cc -Wall -g printf.c -o printf but I'm getting this warning: printf.c:2:1: warning: return type defaults to ‘int’ [-Wreturn-type] it compiles the code and I get the desired output but I want to understand what this means main() should be int main() In C89, the default return type is assumed to be int , that's why it works. In C89, the default return type is

In my app I have a fair number of entities which have fields which are getting their values set via reflection. (In this case NHibernate is setting them). I'd like to get rid of the "x is never assigned to and will always have its default value 0" warnings, so I can more easily pick out the other warnings. I realize you can surround them in pragma directives, but AFAIK you have to do this for each one. Is there a project wide or solution wide way I could do this? Use the C# commandline option /nowarn http://msdn.microsoft.com/en-us/library/7f28x9z3(VS.80).aspx To do this within visual studio

This code illustrates something that I think should be treated as bad practice, and elicit warnings from a compiler about redefining or masking a variable: #include <iostream> int *a; int* f() { int *a = new int; return a; } int main() { std::cout << a << std::endl << f() << std::endl; return 0; } Its output (compiled with g++): 0 0x602010 I've looked at a couple references (Stroustrup and The Complete C++ Reference) and can't find anything about when and why this is allowed. I know that it's not within a single local scope, though. When and why is this allowed? Is there a good use for this

I have this warning: Warning 3 Ambiguity between method 'Microsoft.Office.Interop.Word._Application.Quit(ref object, ref object, ref object)' and non-method 'Microsoft.Office.Interop.Word.ApplicationEvents4_Event.Quit'. Using method group. on my line wordApplication.Quit(); I have tried replacing it with: wordApplication.Quit(false); // don't save changes and wordApplication.Quit(false, null, null); // no save, no format but it keeps giving me this warning. It's not a huge problem because the code compiles perfectly and functions as expected, but I'd like to get rid of the warnings. What can I