> On 19 Aug 2016, at 01:50, Chuck Burgess <demon.g...@gmail.com> wrote: > > I have to concur with those who classify this akin to "tabs vs spaces", as: > - neither choice significantly hinders coding > - either choice could win a vote today and lose a revote in several months > > I see this as one of those "pick one and be done, stick with it, and focus on > harder stuff”. > I see it quite similar.
Sure it can make your signatures quite long but if this hits the limits of your screen width you have other issues. I do agree that not allowing a postfix can encourage better named classes rather than the common overly generic names. Less generic names would also help differentiate my tabs in my IDE, having the Interface is however also a “solution” to this. As for the argument that “Interface” might also be part of the namespace, this seems like more of the same, ie. if you currently group your interfaces into a separate namespace, then you are doing the same thing as the postfix, just in a different flavor. So in the end it all boils down to, not important enough for me to care but important enough that consistency is appreciated. As a result I see no point in changing. regards, Lukas Kahwe Smith sm...@pooteeweet.org -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscr...@googlegroups.com. To post to this group, send email to php-fig@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/7DBDAEE3-070B-4BD3-BB2C-9969E90ACCFF%40pooteeweet.org. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
