delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
To: | cygwin AT cygwin DOT com |
From: | "Mikael" <mindcooler AT gmail DOT com> |
Subject: | Warnings for converting non-pointer types to NULL |
Date: | Thu, 12 May 2005 17:01:37 +0200 |
Lines: | 17 |
Message-ID: | <d5vqlp$k4$1@sea.gmane.org> |
X-RFC2646: | Format=Flowed; Original |
X-IsSubscribed: | yes |
Hello, I'm using Cygwin to develop programs using Win32 for the GUI and lot's of posix stuff for the "back-end". Anyway, I noticed that if I include <windows.h> in a file, I have to include <cstddef> after it if I want to receive warnings for converting non-pointer types to NULL. I guess presume NULL is a macro evaulting to 0 in windows.h and a typedef for (void *)0 in <cstddef>, or? Since I want to have this warning, the approach I've taken is to always include <cstddef> after <windows.h>. Is approach correct and safe or can it get me in trouble? Thanks for any replies / M -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |