[ODE] Trimesh vs Convex Hull

[Rodrigo Hernandez]

I am with Jon on this one, trunk should be for active development, tags, 
branches and releases should be for either taking a whole new direction, 
or to frezze the code at some point in time, only adding
the most critical bugfixes to it.

Now, I can #ifdef all you want, but IMO the default would be to compile 
that code IN rather than OUT, if the code breaks something else, you 
have the option to turn it off
(in this case, it shouldnt happen since its all brand new code), the 
reason being that if future patches and additions break the #ifdef code, 
and it is turned off by default, the chances
of someone noticing, and thus fixing it get reduced by a lot.

Oh, by the way, autotools for MinGW is broken (dlls, Cylinder and 
Opcode) , thats why I couldn't commit the convex stuff yesterday, I'll 
fix it first, then move on on the
re-arrangement of collision_std, and finally merge my code, I'll try to 
fix it for MACOS on the way, but remember, I have no way of knowing if 
it will work.

Cheers!

Jon Watte (ODE) wrote:

> J. Perkins wrote:
>
>>> I dislike #ifdef code a lot. That's what you have branches for. If we
>>> have a "trunk" and a "working" branch in SVN, then commit to working,
>>
>
>> My $0.02 is that putting it in a branch means that someone is going to
>> have to do extra work to keep it sync with the trunk, and users have
>
>
> The way the branches are in SVN, we have the stable (0.6), and we have 
> the unstable (it's the trunk). Thus, I think that new developments 
> that work and pass testing (even though they don't implement 
> everything yet) should right now go on trunk.
>
> No #ifdefs necessary. Make sense?
>
> Cheers,
>
>             / h+
>