[ODE] 0.8.2 candidate
oder at eleks.lviv.ua
Fri Sep 28 01:53:23 MST 2007
Some warnings reappeared because I commented explicit casting to float
during my changes in code that passed parameters to OPCODE. As a quick
resolution I would prefer disabling warnings. However casting to float is a
pretty bad solution. This would make it impossible to track down all the
incorrect casts on in callers if some floating point type customization
would be implemented in OPCODE. The correct approach is to define some type
alias (e.g. opc_float or opReal) as float and cast to it. Then if there
would be type changes in OPCODE in future it would be possible to just
re-define that type alias to new native OPCODE type.
-- ICQ: 36361783
----- Original Message -----
From: "Jean-Sébastien Guay" <jean-sebastien.guay at polymtl.ca>
To: <ode at ode.org>
Sent: 28 вересня 2007 р. 00:09
Subject: Re: [ODE] 0.8.2 candidate
> Hello Jason and Jon,
> Jason Perkins said:
>> It is a non-trivial amount of work to untangle
>> that one, but everyone would sure appreciate it if someone took it on.
> Jon Watte said:
>> The thing is that the warnings may be helpful when porting to 64-bit,
>> so casting them away would be a disservice.
> Ok, so 2 differing opinions. I have never ported an application (let
> alone a library) to 64-bit, so I wouldn't know about what Jon says,
> but I've always hated pragmas almost as much as warnings... Anyways,
> if no one insists on taking the decision to fix them, I'll defer to
> Jon's knowledge and experience on this one.
> Anything on the demo_heightfield crash, and the new trimesh-trimesh
> code's assertion failure?
> Jean-Sebastien Guay jean-sebastien.guay at polymtl.ca
> This message was sent using IMP, the Internet Messaging Program.
> ODE mailing list
> ODE at ode.org
More information about the ODE