Re: Exceptions for method on non-object rather than fatal (desired feature?)

From: Date: Tue, 21 Feb 2012 18:03:43 +0000
Subject: Re: Exceptions for method on non-object rather than fatal (desired feature?)
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message 
I see no reason why it would be not desirable to have PHP raise the
exception rather than putting more or less repeating code snippets all
around the place. That is why I am asking.


You must be returning false/null somewhere. It's the same effor to
instead throw an exception or to return a Ghost family member.


The $baby->mother() method cannot know if the using code just wants to collect the $mother object or execute code on it. It can also not know if having no $mother is a problem or just a fact to deal with. Unconditionally raising an exception is a bit overkill here, at least if we would get an exception for trying to access (null)->mother();

Currently the user code must check each link of the chain if it is available, although it is only interested if it can get the final result or not.

I'll follow the suggestion and write an RFC.

-- 
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: [email protected]

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

Thread (18 messages)

« previous php.internals (#57923) next »