Re: [PHP] Seemingly incorrect strict standard.

2013-06-04 Thread Richard Quadling
On 4 June 2013 09:57, Richard Quadling wrote: > On 3 June 2013 20:37, shiplu wrote: > >> Show a short reproducible code. >> > And I can now see an interface is a much simpler mechanism! > getMessage(), PHP_EOL; } try { $o2 = new sub2('Stuffed2'); } catch(Exception $ex){ echo $ex->getMe

Re: [PHP] Seemingly incorrect strict standard.

2013-06-04 Thread Richard Quadling
On 3 June 2013 20:37, shiplu wrote: > Show a short reproducible code. > Short-ish ... getMessage(), PHP_EOL; } try { $o2 = new sub2('Stuffed2'); } catch(Exception $ex){ echo $ex->getMessage(), PHP_EOL; } ?> And I can now see an interface is a much simpler mechanism! -- Richard Quad

Re: [PHP] Seemingly incorrect strict standard.

2013-06-03 Thread shiplu
Show a short reproducible code.

Re: [PHP] Seemingly incorrect strict standard.

2013-06-03 Thread Richard Quadling
Aha! Don't make it abstract in my base class, but I can throw an exception (perfectly reasonable for me as the called class should implement the method). On 3 June 2013 18:36, Matijn Woudt wrote: > > On Mon, Jun 3, 2013 at 7:24 PM, Richard Quadling wrote: > >> Hi. >> >> I've got an abstract cl

Re: [PHP] Seemingly incorrect strict standard.

2013-06-03 Thread Matijn Woudt
On Mon, Jun 3, 2013 at 7:24 PM, Richard Quadling wrote: > Hi. > > I've got an abstract class which requires one of the concrete descendants > to implement a static function. > > The base class will call it using static:: rather than self::. > > But I'm getting an error at runtime. > > Static funct