On Thu, Feb 2, 2012 at 7:28 AM, D. J. info...@gmail.com wrote:
I think in the Interface in FooInterface should be referred to interface
declaration while Abstract in FooAbstract referred to abstract
declaration, which makes it more meaningful and consistent both in naming
convention and in
It is true that the concept abstract is an adjective in PHP, however in
the context of Foo, Interface, Abstract, the FooAbstract in
FooAbstract.php does play the role of declaration of Foo Abstract, a
compound noun, same as FooInterface.
On Thu, Feb 2, 2012 at 5:11 PM, Artur Bodera
Agreed.
Consistent naming convention with consistent prefix or suffix makes it
better to group relevant files.
Otherwise you will find it messy:
...
AbstractFoo.php
BooSomethingA.php
BooSomethingB.php
FooInterface.php
Foo.php
FooTrait.php
On Thu, Feb 2, 2012 at 5:31 PM, Andreas Möller
Regardless other arguments, I do think it a valid advantage for grouping
files to use suffix for all, including Interface, Abstract and future Trait.
Hope Ralph can take this into account.
On Thu, Feb 2, 2012 at 5:37 PM, D. J. info...@gmail.com wrote:
Agreed.
Consistent naming convention with
-- Andreas Möller a...@softe.is wrote
(on Thursday, 02 February 2012, 10:56 AM +0100):
Regardless other arguments, I do think it a valid advantage for
grouping files to use suffix for all, including Interface, Abstract
and future Trait. Hope Ralph can take this into account.
Using
-- Sascha-Oliver Prolic saschapro...@googlemail.com wrote
(on Thursday, 02 February 2012, 12:06 PM +0100):
I would like to keep interface names like serializable, countable,
etc. Is this proposal also about getting rid of them?
That's one of the options available on the poll (keep the status
I think in the Interface in FooInterface should be referred to interface
declaration while Abstract in FooAbstract referred to abstract
declaration, which makes it more meaningful and consistent both in naming
convention and in English
+1 (This is what I voted, too).
Apart from this, when
Hello,
Before you vote, I suggest you read my RFC as to why this is coming up
again:
http://framework.zend.com/**wiki/x/jQHbAQhttp://framework.zend.com/wiki/x/jQHbAQany
try to understand the issues that the current scheme have brought to
the forefront. I'd also suggest that if you're a
2012/2/2 Andreas Möller a...@softe.is
I think in the Interface in FooInterface should be referred to
interface
declaration while Abstract in FooAbstract referred to abstract
declaration, which makes it more meaningful and consistent both in naming
convention and in English
...
right
Regardless other arguments, I do think it a valid advantage for grouping
files to use suffix for all, including Interface, Abstract and future Trait.
Hope Ralph can take this into account.
Using suffixes also takes into account the naming style in ZF1 with PHP 5.3:
Foo_Bar_Baz_Abstract
I would like to keep interface names like serializable, countable,
etc. Is this proposal also about getting rid of them?
Regards
Sascha-Oliver Prolic
--
List: fw-general@lists.zend.com
Info: http://framework.zend.com/archives
Unsubscribe: fw-general-unsubscr...@lists.zend.com
Hi Sascha,
The problem with Countable/Serializable and others is that you need an
obvious verb to append able to. Unfortunately, English is not the
most consistent of languages.
Here's a simple example - what would you call the interface shared by
a collection of Filters? You could try
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/
-- Pádraic Brady padraic.br...@gmail.com wrote
(on Thursday, 02 February 2012, 05:49 PM +):
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
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
Hmm, or rather the Nouns that precede the suffixes :P. Sorry, brain is
still asleep today.
On Thu, Feb 2, 2012 at 5:49 PM, Pádraic Brady padraic.br...@gmail.com wrote:
I really don't follow the grouping argument - not all Abstracts,
Interfaces and Traits would share the same Noun. I could have
-- Tomáš Fejfar tomas.fej...@gmail.com wrote
(on Thursday, 02 February 2012, 09:14 PM +0100):
Well in this case:
I could have an
AHtmlSanitiser implementing IFilter making use of
several THtmlMarkups.
Works for me fine :D
I'd argue that's unreadable. :)
I understand the consistency
Well in this case:
I could have an
AHtmlSanitiser implementing IFilter making use of
several THtmlMarkups.
Works for me fine :D
On Thu, Feb 2, 2012 at 7:02 PM, Matthew Weier O'Phinney matt...@zend.comwrote:
-- Pádraic Brady padraic.br...@gmail.com wrote
(on Thursday, 02 February 2012, 05:49
Perhaps for you, for me it looks and sounds awkward ;).
2012/2/2 Tomáš Fejfar tomas.fej...@gmail.com:
Well in this case:
I could have an
AHtmlSanitiser implementing IFilter making use of
several THtmlMarkups.
Works for me fine :D
On Thu, Feb 2, 2012 at 7:02 PM, Matthew Weier O'Phinney
-- Andreas Möller a...@softe.is wrote
(on Thursday, 02 February 2012, 09:45 PM +0100):
Perhaps for you, for me it looks and sounds awkward ;).
Similar to suffixing in one place and prefixing in another.
You completely ignored or overlooked the next paragraph, where I talk
about natural
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
Perhaps for you, for me it looks and sounds awkward ;).
Similar to suffixing in one place and prefixing in another.
Andreas
--
List: fw-general@lists.zend.com
Info: http://framework.zend.com/archives
Unsubscribe: fw-general-unsubscr...@lists.zend.com
I'd argue that's unreadable. :)
I understand the consistency argument, but I also am a proponent of
natural language constructs in programming, as I feel they make code
easier to read and understand. I'm okay with a little inconsistency if
it enables readability.
But does it?
You may have
There you've got proof that using a noun as an adjective is not
unnatural at all:
http://www.englishclub.com/grammar/nouns-adjective.htm
Andreas
--
List: fw-general@lists.zend.com
Info: http://framework.zend.com/archives
Unsubscribe: fw-general-unsubscr...@lists.zend.com
Suffixing there and prefixing here doesn't improve readability whatsoever.
There's no need to be absolutist - several people have already stated
it improves readability for them.
Paddy
On Thu, Feb 2, 2012 at 8:51 PM, Andreas Möller a...@softe.is wrote:
I'd argue that's unreadable. :)
I
This is one of those damned if you do, damned if you don't things. It ends up
being personal preference.
Personally, I prefer:
ZonkAbstract
ZonkInterface
ZonkTrait
Some prefer:
AbstractZonk
ZonkInterface
ZonkTrait
Ultimately, I don't care. It would take me 2 seconds to learn and remember
I'll try and sum up what we discussed in #zftalk.2 today.
For instance; I am having some issues understanding some of the votes.
My main concern is ultimately consistency in the naming of itself and
there seems like there might be an option missing as well. From my
point of view having an
On Thu, Feb 2, 2012 at 12:09 PM, Ralph Schindler
ra...@ralphschindler.comwrote:
I'll try and sum up what we discussed in #zftalk.2 today.
For instance; I am having some issues understanding some of the votes.
My main concern is ultimately consistency in the naming of itself and
there
28 matches
Mail list logo
