1. Nah, you'll forget to remove it, or miss a place or two in the code. trigger_error() is the way (it is controlled by the same error reporting mechanisms that should let error reporting be on in development and off on release)
2. Yes, but it may not suit the business logic all the time. You gotta be careful when you apply this.
Protected from injection? You decide.
Moderator: General Moderators