Fix #79168: Missing __construct method documentation in SPL Exceptions

[carusogabriel]

Generalizing the Exception::__construct documentation to methodsynopsis
instead of constructorsynopsis will include it in SPL Exception queries.

[cmb69]

The current status is that we want to <xi:include> both (and also the <destructorsynopsis> if available), see http://svn.php.net/viewvc/phpdoc/doc-base/trunk/RFC/skeletons/classname.xml?view=markup. Also an <xi:fallback /> should be inserted as child element (otherwise missing elements would error). Unfortunately, this doesn't prevent a notice/warning (from configure.php or PhD), so we better avoid adding <xi:include>s for elements which don't exist.

[carusogabriel]

@cmb69 So the action point here is to add <xi:include /> of constructorsynopsis to all SPL Exception with an <xi:fallback />?

[cmb69]

Yes. Basically like http://svn.php.net/viewvc?view=revision&revision=345155.

[carusogabriel]

ping @cmb69 just to make sure everything is okay and we can merge this one :)

[cmb69]

Thanks for the ping!

The actual fix is fine, so I've applied it as http://svn.php.net/viewvc?view=revision&revision=349537.

Whitespace changes are a particular issue for the English docs, though, since these make the updates harder for translators to catch up; therefore I did not commit this part. Not sure if these should ever be done on a "large" scale. If all (active) translation were up-to-date, this could be done for all languages in one go (using a script which updates the EN-Revisions automatically), but this is unfortunately not the case. If you feel strongly enough regarding this cosmetic fix, I suggest writing to the docs mailing list – maybe a suitable solution can be found.