If it's fatal, there's no issue. What I'm worried about is the
suggestion made earlier that non-fatal errors,
Then use @mysql_connect(...)
E.g., exception-aware code uses old exception-unaware code
somewhere inside a try {} and the error handling would all get skipped
as the exception unwinds all the way out of the old code.
It is the sense of exceptions that you do not need other error handling.
I'm all for non-fatal errors in internal functions throwing exceptions,
it's the right way to go, but want to see it solved in a way that
doesn't needlessly add danger to mixing in older code.
Good to hear :-)
marcus