Order functions in binary up to the end of Helicopter
; refactor vector/matrix classes
#1309
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR attemps to order functions in the recomp binary according to how we find them in the original. To make this work, I had to extensively refactor the vector/matrix classes and separate declaration from definition.
The order now looks like:
There is one anomaly around the beginning of the
Helicopter
class, whereMx4DPointFloat::operator=
appears to be situated in betweenHelicopter::IsA
and the scalar ddtor. I haven't found a way to fix that yet.The other inaccuracy in order is because of
Helicopter::FUN_100042a0
, which isn't fully matching and has some incorrect inlining. This should line up once the function is fully matched.Before this can be merged, we still need to figure out the detection of the function annotation of
Matrix4::GetData
(@disinvite )