Crymson wrote:WTF ?
The patch that I did, did not make anything less readable nor unmaintainable. It wasn't a hack either. It will be used to find out where the problem is coming from, since the pointers were getting out of bounds. That in turn helps you find the real location of the problem.
Sorry you can't understand basic debugging practices. Then again, if you did, then you wouldn't need to write a fix multiple times.
Okay, okay, it was a good patch, I misspoke. I still think you should've used
#defines. And detecting that a pointer's corrupted doesn't really help unless you can detect when it became corrupted, which is why we've had very little progress fixing all those corruption bugs yet.
Crymson wrote:If you don't know how, then you learn, and try adding more code to narrow the problem down--You know, like the patch I did.
Your one smug elitist.
See above. Practically all of our remaining bugs are memory corruption bugs, for which detecting that parts of memory are corrupted really doesn't help narrow down when/how it became corrupted.
Furthermore, if an elitist is someone who contributes to an open-source project but doesn't fix exactly the bugs you tell them to fix, then pretty much everyone here but Buginator is an elitist.
You know why I don't fix bugs as often lately? Because I've already fixed all the ones I know how to fix. Nowadays, all I fix are regressions, and currently, there are only a few of those, and those happen to be pretty high on my priority list. When I joined the project, my expertise was on balance, website improvement, and UI. And that's also what most of my current feature patches are: fixes for UI bugs. I do wish to eventually learn how to fix these harder-to-fix bugs, but is it so wrong for me to do what I'm good at, instead of dropping everything and working on what you tell me to?
Crymson wrote:Have it you way, have fun with the project, I know I won't be doing anything anymore, it isn't worth wasting anymore of my time.
I'm not entirely sure what you mean by that.
You're going to leave the project because you disagree with
me? It's not like I lead the Project. It's not like I ever overrule anyone else when I disagree with them. I may not say it often, but I encourage people to voice contrary opinions when they disagree with me.