-- Pádraic Brady <[email protected]> wrote
(on Thursday, 02 February 2012, 05:49 PM +0000):
> I really don't follow the grouping argument - not all Abstracts,
> Interfaces and Traits would share the same Noun. I could have an
> AbstractHtmlSanitiser implementing a FilterInterface making use of
> several HtmlMarkupTraits. Actually that whole last sentence just shows
> why English ordered terminology works. If you want to enforce
> grouping, you'll also need to enforce the Nouns that follow the
> suffixes to be suitably similar and alphabetical.

That's an argument I've been meaning to make as well -- thanks for
verbalizing it so well, Paddy.


> On Thu, Feb 2, 2012 at 3:28 PM, Andreas Möller <[email protected]> wrote:
> >>> Using suffixes also takes into account the naming style in ZF1 with PHP < 
> >>> 5.3:
> >>>
> >>> Foo_Bar_Baz_Abstract
> >>> Foo_Bar_Baz_Interface
> >>
> >> I think this is a red herring. The above doesn't map the same at all, as
> >> in ZF1 we were able to group them in a directory together:
> >>
> >>    Foo/
> >>        Bar/
> >>            Baz/
> >>                Abstract.php
> >>                Interface.php
> >>
> >> We can't do likewise in ZF2 as we can't have classes/interfaces named
> >> "Abstract" or "Interface" -- and hence the need for new naming
> >> conventions.
> >
> > Indeed, but why should we do it totally different?
> >
> > The argument with the grouping holds, as suffixing class names would
> > allow for grouping, too.
> >
> > This argument weighs in a lot more than the grammatical argument.
> >
> > And again, it's consistent. You commented on the RFC likewise.
> >
> >
> >>
> >
> > Andreas
> >
> 
> 
> -- 
> Pádraic Brady
> 
> http://blog.astrumfutura.com
> http://www.survivethedeepend.com
> Zend Framework Community Review Team
> 

-- 
Matthew Weier O'Phinney
Project Lead            | [email protected]
Zend Framework          | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc

--
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]


Reply via email to