3 ms·
I make little mistakes like this all the time in a massive code base. What I do is do a diff on the code to see what's changed. Much easier than hunting through
by zikzak 8y ago
I make little mistakes like this all the time in a massive code base. What I do is do a diff on the code to see what's changed. Much easier than hunting through. This applies any time it "should work" but does not.
Also, I am sorry you have to work in an environment like that.
- keanebean86 8y agoI mixed up l and I in my ldap function in some php code. I'm not sure if it was the framework (fat free) or something else but that function would never throw any errors or exceptions. It was maddening and took at least a day to notice. I started questioning my sanity. I never thought to just do a diff...
- ZeroCool2u 8y agoSomething that also helps cut down on these types of bugs for me is Semantic Highlighting. I've gotten my whole team to use it. It's great, because you don't have to read the var name, you just have to see if there's any var in a function that doesn't have the same color as anything else and they tend to stick out like a sore thumb. Not sure if that's the best explanation, but if you're using any JetBrains IDE you can try it by going to Settings and searching for Semantic Proximity and hitting the check mark. Easier to show than explain.
- flyinglizard 8y agoI’ve once had a non printable in a header file on a huge codebase (mobile phone OS and apps, pre-iPhone) :(