Re: PEAR2 package naming standards (namespace usage)

On Mon, Sep 1, 2008 at 11:34 AM, Travis Swicegood <development@domain51.com> wrote: > (...) > This is warranted by the lack of adoption by anyone outside PEAR and in some > cases open hostility toward the PEAR naming schema by those same people. > Zend Framework and SolarPHP are the only two packages outside of PEAR that > I know that use the PEAR naming schema. I have recommended the idea in > companies where I have worked with developers that don't have a PHP > background and have met with resistance. "It's too verbose," "It's > too hard > to explain to new developers," "It's overly complex when simple directories > work," etc. We obviously all work for different people - my point is. I've never seen/experienced such hostility. I've followed the PEAR naming scheme on pretty much every project I've worked on in the past three years. Point taken - for example sometimes it seems overkill adding a new directory for an Exception.php, but what's the trade off here? A few bytes vs. a clear naming scheme? I'd go the extra mile if that allows me "think" less and get back to productivity faster if I haven't dealt with the code for a couple months/years. Till