I am not sure about the osg coding protocol, but for what we do at my work
place we use size_t as the generic "unsigned int"... this will be unsigned
long for win32 and __int64 for the x64 platform. It is good to use as a
generic container for local variables since it chooses the native size that
fits best per platform. size_t is great for pointer offsets too.
The part that is unclear to me is the osg protocol in regards to using
things like size_t fpos_t etc... osg has to be more generic to comply to
all platforms, and this is something I have not needed to worry about (yet).
James Killian
----- Original Message -----
From: "Mario Valle" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, June 25, 2008 12:02 PM
Subject: [osg-users] Warning on 64bits: cast to pointer from integer
ofdifferent size
On x86_64 (Suse 10.3) the following warning appears at lines 431 and 600
of BufferObject.cpp :
"warning: cast to pointer from integer of different size"
In both places (few lines over), if I change the line:
unsigned int offset = 0;
to:
unsigned long offset = 0;
The warning goes away.
Can anyone more knowledgeable than me confirm that the change is correct
before I submit the change?
Thanks!
mario
--
Ing. Mario Valle
Data Analysis and Visualization Services |
http://www.cscs.ch/~mvalle
Swiss National Supercomputing Centre (CSCS) | Tel: +41 (91)
610.82.60
v. Cantonale Galleria 2, 6928 Manno, Switzerland | Fax: +41 (91)
610.82.82
</div>
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org