delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1999/02/05/14:10:40

Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: jmm AT raleigh DOT ibm DOT com
Message-Id: <199902051339.IAA19909@jmm.raleigh.ibm.com>
Subject: B20.1: typedef for DWORDLONG
To: cygwin AT sourceware DOT cygnus DOT com
Date: Fri, 5 Feb 1999 08:39:38 -0500 (EST)

I've never done Win32-based programming before and I'm having to modify
someone else's NT 4.0 app to do some signal handling and noticed that
while trying to compile with B20.1, their code uses DWORDLONG as a 
64-bit integer type (appears to be equiv to LONGLONG I think?).  Thinking
maybe it was just their bad programming, I pulled up MS's Visual C++
5.0 and sure enough their code examples use DWORDLONG as a 64-bit
integer type as well.

B20.1's windows32/base.h typedef's it as a double, which considering DWORD
is an unsigned int, doesn't make sense to me.  Am I missing something
about the type assignments (coming from Linux development, it's weird
not to use int, long, long long, but I'm trying not to re-type everything
in this whole app just to work with B20.1 :)

Thanks,

James Manning
-- 
Hardware Design Engineer --- IBM Netfinity Performance Development

--   
Want to unsubscribe from this list?                             
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com


- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019