by Graf Zahl » Fri Nov 06, 2020 12:55 am
Don't worry, we'll find those things. It was to be expected that there's some problems.
BTW, I started with similar work on Blood. But that code is in a different league. Instead of spreading actors across two arrays, Blood has seven! This is one of the main reasons why the actor code looks so messy - it needs to play around wil lots of pointers to get things done, and to top it off, some of the added data is optional, meaning the code is also full of rather needless checks for the presence of these, too...
The positive is that it contains less spaghetti code - it's not free of that and the spaghetti that's present is even worse than Duke, but the amount is limited to a handful of functions, not the dominant style throughout.
Don't worry, we'll find those things. It was to be expected that there's some problems.
BTW, I started with similar work on Blood. But that code is in a different league. Instead of spreading actors across two arrays, Blood has seven! This is one of the main reasons why the actor code looks so messy - it needs to play around wil lots of pointers to get things done, and to top it off, some of the added data is optional, meaning the code is also full of rather needless checks for the presence of these, too... :?
The positive is that it contains less spaghetti code - it's not free of that and the spaghetti that's present is even worse than Duke, but the amount is limited to a handful of functions, not the dominant style throughout.