Proposed texture coord change and compatibility with MinGW 4.7.x and Boost.Thread 3.x.x

[stonedcoldsoup]

• Fixed issues with unqualified names in MinGW 4.7.x by explicitly qualifying boost::intrusive_ptr*.
• Fixed issue with Boost.Thread 3.x.x crashing on exit in the garbage collector upon trying to join the thread. As of Boost.Thread 3.x.x, you must call joinable() to determine if the object can be joined before calling join(), as attempting to call join() on an unjoinable() thread throws an exception and can't be recovered from in some cases.
• Texture coordinates now have 4 elements instead of 2. This is a very minimal change, though it doubles the memory footprint of texture coordinates. The advantage is that if you want to do perspective correct texturing (say, in a 2.5D style game) as I do, you can. I think somebody might find it useful.
• Fixed annoying initializer list reorder warnings.

[theacodes]

I'm going to accept all of the changes with the exception of the Texture Coords changes. Reason being is that we have overarching plans with the experimental renderer to allow a pluggable architecture.

[stonedcoldsoup]

Oooh, that's the ticket! Pluggable is (nearly) always better. I did a dynamic vertex format experiment once. Is that the road you're considering? Let me open a suggestion.