64bit builds

[Numpsy]

I've got it mostly building ok now in GDC 4.6 1/32bit (including running a couple of the examples), but there are loads of errors when trying to build in 64bits.

Some of the errors are things like passing size_t to WinAPI functions that always take 32bit numbers, but there are a bunch of places where it assigns array.length to an int, which causes ulong->int conversion errors. These need to looked at the see the best way to fix them.

[JesseKPhillips]

Thinking about this, and not actually looking at the situations. I would think assigning array.length should go to a size_t. Calls to Windows Functions should have the number converted via to!uint() as this will check for overflow during conversion. Unless Windows has a way to take 64bit for its calls or there is some way to know the conversion is always valid, I think that is the best choice.