note 52329 added to language.oop5.reflection
| From: | walter dot huijbers at gmail dot com | Date: | Thu, 28 Apr 2005 00:28:21 +0000 |
| Subject: | note 52329 added to language.oop5.reflection | ||
| Groups: | php.notes | ||
| Request: | Send a blank email to php-notes+get-88667@lists.php.net to get a copy of this message | ||
The wonderfull example code of russ collier works great until using it in combination with an
interface or another abstract class, wich forces to define a function or variable in the loadable
dynamic class, and the loaded class doesn't implement all the abstract functions. Ofcourse the
class should not be used and an error should be reported, but the reported error is a Fatal error
and is impossible to catch. This way it is impossible to, for example, generate an error message
displaying the name of the file from wich the class is loaded.
Having dynamicly loadable classes with a forced interface can be very usefull when working on big
projects or giving third parties the ability to provide new plugins. Considering this (imho) it
would be nice to provide a clean error message to the writer of the plugin.
Please correct me if I'm wrong.
----
Manual Page -- http://www.php.net/manual/en/language.oop5.reflection.php
Edit -- http://master.php.net/manage/user-notes.php?action=edit+52329
Delete: added to the manual -- http://master.php.net/manage/user-notes.php?action=delete+52329&report=yes&reason=added+to+the+manual
Delete: bad code -- http://master.php.net/manage/user-notes.php?action=delete+52329&report=yes&reason=bad+code
Delete: spam -- http://master.php.net/manage/user-notes.php?action=delete+52329&report=yes&reason=spam
Delete: useless -- http://master.php.net/manage/user-notes.php?action=delete+52329&report=yes&reason=useless
Delete: other reasons -- http://master.php.net/manage/user-notes.php?action=delete+52329&report=yes
Reject -- http://master.php.net/manage/user-notes.php?action=reject+52329&report=yes
Search -- http://master.php.net/manage/user-notes.php