RE:[CINT] Re: [ROOT] Long_t/ULong_t in Wind

From: Masaharu Goto (MXJ02154@nifty.ne.jp)
Date: Tue Jun 11 2002 - 14:13:10 MEST


Hello,

Cint with Visual C++ has __int64 wrapper class G__longlong and it is 
typedefed as 'long long'.  If you use 'long long' in interpreted code,
it works as __int64. If you want to use the name __int64, please 
typedef G__longlong as __int64 after loading include/long.dll. long.dll
is generated as cint optional library under lib/longlong directory.

Thank you
Masaharu Goto


>Date: Tue, 11 Jun 2002 08:25:39 +0200 (METDST)
>From: Rene Brun <Rene.Brun@cern.ch>
>To: gmoloche@mit.edu
>Cc: cint@pcroot.cern.ch, roottalk@pcroot.cern.ch
>Subject: [CINT] Re: [ROOT] Long_t/ULong_t in Windows
>
>Long_t and ULong_t are currently non portable data types.
>The ROOT I/O sub-system is already using 64 bits for these data types,
>independently if the in memory data type is 32 or 64 bits.
>We are waiting the support for longlong in CINT to introduce a truely
>portable data type in ROOT (let's call it Long64_t).
>
>Rene Brun
>
>On Mon, 10 Jun 2002 gmoloche@mit.edu wrote:
>
>> Hello,
>> 
>> This is to report a bug. Long_t and ULong_t are the same as Int_t and UInt_
t in 
>> the windows version of ROOT.
>> 
>> For the time being I am using __int64 and unsigned __int64 in ACLIC, 
compiling 
>> with visual C++ 6.0. The only problem is that CINT doesn't know what __int6
4 is.
>> 
>> Thanks. 
>> 
>



This archive was generated by hypermail 2b29 : Sat Jan 04 2003 - 23:50:56 MET