Make Plasma 64-bit compliant about plasma HOT 7 CLOSED

Lots of 32-bit assumptions in the max plugin are going to make this painful for me <.<

from plasma.

This is a must both for future plugin compatibility and for making porting easier - Linux especially much prefers the native architecture.

from plasma.

The first steps are being taken here as we're working on Linux support. We've already resolved the biggest issue (use of long for 32-bit integers).

from plasma.

What's the break down of what qualifies for 64-bit compliant as it pertains to this codebase?

from plasma.

The issue that sticks out the most to me is that Cyan used 32-bit vector indices everywhere. That's not too terrible but sill not good. @zrax mentioned the other day that parts of the network code will likely explode in 64-bit.

from plasma.

32-bit vector indices won't break, they'll just cause lots of warnings. My biggest concern would be anything that assumes longs are 32-bit (always true on windows64, but not on unix 64), or anything that stores a pointer in an integer.

This issue is "complete" when we can build a 64-bit client without errors, and have it run without crashing.

from plasma.

The lack of a 64-bit PhysX is also going to bite us here. With just a few tweaks to update Windows API calls I can get the entire solution (excluding the Max plugin) building for 64-bit except plPhysX. Until we replace that (#4), we can't even build a client.

from plasma.