> > > > What is consistent and exists on the internal language layer > > not necessarily good for the user-land. I'm kind'a surprised no one > thought > > of that. > > As I said I can live with the throwing notices and warnings (and not > > E_RECOVERABLE_ERROR as I personally wanted), but returning false even not > > trying to run the function is just a bad idea all over the place. > > I'm confused. Do you not want E_RECOVERABLE_ERROR for parameter > failures? Or do you, but could live with lesser as well? I didn't > quite get that part... > > Anthony > Hi Anthony.
Yea, that part looks confusing. What I wanted to say is that I would like to get E_RECOVERABLE_ERROR and I was voicing my opinion on that earlier in the threads. But I could live with E_WARNING and E_NOTICE if community decides it to be less strict - I will clean up my code not to throw a single notice (and because I use Yii - it's by default converts any E_* raised to a fatal error and throws HTTP 500 error via exceptions). In my 8 years of active PHP development I learned that some strictness in deep core code of the project is a good thing and erroring the hell out there makes perfect sense. It's a delicate balance and I never apply it to the level that does actual communication with the outside world.
