On 25 May 2010 19:37, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: > On Tue, May 25, 2010 at 13:08, Richard Quadling > <rquadl...@googlemail.com> wrote: >> On 24 May 2010 16:00, Hannes Magnusson <hannes.magnus...@gmail.com> wrote: >>> On Mon, May 24, 2010 at 03:25, Philip Olson <phi...@roshambo.org> wrote: >>>> >> At this stage, I'm wondering why we don't simply collect all the errors ... >> >> <?php libxml_use_internal_errors(true); ?> > > I thought we did? Unless --enable-xml-details was set
Then how are the warnings being displayed on the online editor from the xinclude() call? And then the penny drops. The editor is using --disable-segfault-error to NOT capture the errors. http://svn.php.net/viewvc/web/doc-editor/trunk/php/conf/project.php.ini?view=markup#l25 So, if we are not interested in xinclude errors, captured by libxml_use_internal_errors(true) or otherwise, then a simple @$dom->xinclude(); libxml_clear_errors(); should do the trick. >> Currently, final private methods are documented as part of the class >> (http://docs.php.net/LogicException for example). >> >> The __clone() method is neither part of nor callable from any >> sub-class of Exception and shouldn't be documented as such. > > It isn't documented as method of that class, it is documented as > inherited method. > It needs to be there because its a final method. If you create an > exception extending LogicException you cannot declare a method called > __clone(). > > > -Hannes > Of course. I read it completely wrong. Missed the "Inherited" part on the docs. Are you _sure_ you want me playing around with all of this?!!!? -- ----- Richard Quadling "Standing on the shoulders of some very clever giants!" EE : http://www.experts-exchange.com/M_248814.html EE4Free : http://www.experts-exchange.com/becomeAnExpert.jsp Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 ZOPA : http://uk.zopa.com/member/RQuadling
