Comments

Um... there's already a note saying that they could be renamed in future versions. What more do you feel needs to be added, exactly?

The reason why the last segment cannot be Abstract or Interface is that when we change the following:

Zend_Controller_Request_Abstract

to use namespaces, a literal change will leave this:

namespace Zend\Controller\Request;
abstract class Abstract
{
...
}

which leaves that last segment as a reserved PHP keyword, leading to parse errors. We decided simply to pre-empt this and start naming new classes appropriately in preparation for a switch to namespaces.

Matthew, doesn't it make sense if that is what we put in the reference guide? To people who don't know the reasoning behind this, it seems very strange that exactly at this part we deviated from the PEAR standards (this is why this issue was added for).

Posted by Richard George (parsingphase) on 2010-02-16T23:19:00.000+0000

Just a Dolf said; the "what" is specified, the "why" is not. Coders will follow the standard far more happily when they understand the reason behind it. Your explanation here would be ideal as most of us haven't played with namespaces yet.