[edgeless]

Originally Posted by Mark.B

To clarify: nobody's belittling anyone.

Ah, but you were. It was your first line of response to me.

Originally Posted by Mark.B

However, whenever people say "vBulletin is rubbish because it hides errors rather than fixes them" - which is what started to get implied in this thread, as it does in many others -that inaccuracy needs to be corrected, or at the very least, the true facts explained. many do not have the required knowledge to understand what is actually happening, they simply read "vBulletin hides errors rather than fixes them" and assume that to be factual. That perception needs to be corrected.

But the way you go about correcting that perception indeed matters! Your persistent response to my initial use of the terms "errors" and "hiding them" was to assert that I simply don't understand what the SKIP_DS_ERRORS code directive actually does. And then in my subsequent reply when I termed what's being disabled by said code directive as "warnings", you condescendingly went on to imply that my interchanging of the terms confirms my failure to understand what the directive is in fact doing. I think that's quite a leap of an assumption on your part.

So the impression I've taken from your replies in this thread is why I've pointed out that certain vB developers themselves are inclined to characterize the role of the SKIP_DS_ERRORS code line as that of turning off the extra "error reporting". And by the way, fyi, I do understand that non-fatal run-time warnings don't halt the execution of associated functions, and that fatal run-time errors are unrecoverable (i.e., they result in termination of associated functions). It's not a very difficult concept to grasp in my opinion.

Lastly, I think you should be mindful that if I thought vB was "rubbish" I wouldn't likely be using it as a community platform. I hope that's at least some food for thought.