Re: Correct prototype for _findnext()/_findclose()
"Luke Dunstan" <[email protected]> Mon, 29 Mar 2004 09:31:15 +0800
| Newsgroups | gmane.comp.gnu.mingw.patches |
|---|---|
| Message-ID | <[email protected]> |
>From: Danny Smith <[email protected]> >Reply-To: [email protected] >To: [email protected] >Subject: Re: [MinGW-patches] Correct prototype for _findnext()/_findclose() >Date: Sun, 28 Mar 2004 21:05:34 +0100 > > >----- Original Message ----- >From: "Hans Leidekker" <hans-p/[email protected]> >To: <[email protected]> >Sent: Monday, 29 March 2004 02:51 >Subject: [MinGW-patches] Correct prototype for _findnext()/_findclose() > > > > > > _findnext()/_findclose() take a long, not an int. > > > > Documented here: > > > > >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore9 >8/html/_crt__findnext.2c_._findnexti64.2c_._wfindnext.2c_._wfindnexti64. >asp > > >But here, > >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/h >tml/_crt__findnext.2c_._findnexti64.2c_._wfindnext.2c_._wfindnexti64.asp > >we see that l the findnext/close functions use intptr_t. > >Danny The latter documentation is for Visual Studio .NET, but I think we are primarily supporting Visual Studio 6.0 (at least when using msvcrt.dll) so I think it should be "long". It could be conditionally changed to intptr_t when using later versions of the C library, but in cases where it matters (64-bit Windows), I believe intptr_t would be a typedef for "long" anyway, not "int". Luke _________________________________________________________________ What's your house worth? Click here to find out: http://www.ninemsn.realestate.com.au ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click