coapp-developers team mailing list archive
-
coapp-developers team
-
Mailing list archive
-
Message #00675
Re: Engine APIs required by Bootstrap
-
To:
coapp-developers@xxxxxxxxxxxxxxxxxxx
-
From:
"William A. Rowe Jr." <wmrowe@xxxxxxxxx>
-
Date:
Wed, 01 Sep 2010 12:00:11 -0500
-
In-reply-to:
<AANLkTi=S7Sp-TGR6r5XhFAJUrvuPsYyU=1PbNGXMgwK7@mail.gmail.com>
-
User-agent:
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
On 9/1/2010 11:34 AM, Olaf van der Spek wrote:
> On Wed, Sep 1, 2010 at 6:29 PM, Garrett Serack <garretts@xxxxxxxxxxxxx> wrote:
>> Well, Windows APIs use LONG which is a typedef to long .. (clever, eh?)
>> The CRT uses long for things like fseek.
>> off_t is another typedef to long
>> I suppose I should have said long instead of __int64 -- but I have a soft
>> spot for being precise--in spite of the plethora of aliases to long.
>
> You mean long long? Long doesn't cut it.
No... what he describes is LONG. But most win32 API's have two DWORD args,
the extended value would be the signed quadword you are thinking of.
_fseeki64/_lseeki64/_ftelli64 etc are __int64, which is the same as long long
in recent compilers.
References