compiler-warnings

Consider the following code: DateTime t = DateTime.Today; bool isGreater = t > null; With Visual Studio 2010 (C# 4, .NET 4.0), I get the following warning: warning CS0458: The result of the expression is always 'null' of type 'bool?' This is incorrect; the result is always false (of type bool ): Now, the struct DateTime overloads the > (greater than) operator. Any non-nullable struct (like DateTime) is implicitly convertible to the corresponding Nullable<> type. The above expression is exactly equivalent to bool isGreater = (DateTime?)t > (DateTime?)null; which also generates the same wrong

I am involved with a software project written in Qt and built with qmake and gcc on Linux. We have to link to a third-party library that is of fairly low quality and spews tons of warnings. I would like to use -W -Wall on our source code, but pass -w to the nasty third-party library to keep the console free of noise and clutter so we can focus on our code quality. In qmake, is there a way to conditionally add CFLAGS/CXXFLAGS to certain files and libraries? Jonathan, I think the problem is where your source files are including header files from 3rd party libraries, and you want to switch off

My code is as follows package com.foo; public class TestComposition { public static void main(String[] args) { try { Class<Foo> fooClass = (Class<Foo>) Class.forName("Foo"); } catch (ClassNotFoundException e) { e.printStackTrace(); } } } The assignment within the 'try' block results in a warning stating Type safety: Unchecked cast from Class<capture#1-of ?> to Class<Foo> Why is this? Well, to start with let's be clear where the problem is - it's in the cast itself. Here's a shorter example: public class Test { public static void main(String[] args) throws Exception { Object x = (Class<Test>)

VB.NET has this rather annoying limitation which caps compiler warnings reported at 100. vbc : warning BC42206: Maximum number of warnings has been exceeded. This makes things rather frustrating when trying to size up the amount of effort that would be required to comply with VB.NET best practices, such as enabling Option Strict. Is there any way where this limitation could either be removed, adjusted, or could warnings be gathered by some other means (such as through a 3rd party code-analysis tool)? Mark Hurd As of VB11, in VS2012, vbc no longer has a maximum error limit when called from the

I have the following line in my code signed int test_case= -2147483648; which generates the error: C4146 unary minus operator applied to unsigned type, result still unsigned but this is still with the data range of teh signed integer type: __int32 signed, signed int, int –2,147,483,648 to 2,147,483,647 The strange things is assigning it as signed long gives this same error, i.e. signed long test_case= -2147483648; The changes below compile OK: signed int test_case= -2147483647; signed int test_case= 2147483649; signed long test_case= -214748364800; Has anyone seen this issue with Visual Studio