every time a programmer is like "I'll be clever!" someone should stop them
why list the filenames in our archive as a list of strings?
couldn't we save, like, entire kilobytes by instead converting them to a tree of substrings and dynamically traversing it at runtime?
yes you could!
but also consider that your datafile is a total of 38 megabytes on a DVD THAT CAN STORE MANY GIGABYTES
I think they're doing something annoyingly sneaky against the C++ type system.
So they have a function called mbinarySearch and it is heavily overloaded based on final argument's type. There's like 20 variants of it
but every time I see it called, the final argument is NULL
I think they're casting that NULL to a specific type so that they get the right variant of mbinarySearch.
I'm not 100% sure this will work in C++ but it's what I suspect these fuckers are doing
@foone That would totally work in C++, and is a thing often referred to as "tag invoke". It passes in a "tag" which selects the variant to call.
Never thought about how that would reverse engineer, but this seems to match. That's not against the type system though, it's using the type system to do something that it wasn't originally designed for.
