[RyanCahoon]

I don't know of anything in the C++ standard that requires the member initialization list to be in declaration order. It might be some limitation of the compiler, or they might be encouraging that for code readability because the C++ standard does say that no matter the order in the initialization list, the class members will be initialized in the order they are declared in the class definition.

I don't have windriver installed so I can't check to be sure which it might be, but there's nothing keeping you from trying it out. What happens if you reverse the initializers in the example code and try to compile it?