entation and format has none, just.. that's how most
ppl do it.
*Erik Landvall*
*+34 693 74 47 77*
*Skype*
*erik.landvall*
*Hangout*
*erik.landvall*
*Linkedin*
*ErikLandvall* <http://se.linkedin.com/in/eriklandvall/>
2017-03-01 11:55 GMT+01:00 Stefano Torresi :
> @Stefano
&g
@Rivera, I agree with you in full, and this is so fundamental that it's
ridiculous that it even needs to be discussed imho.. The argument ppl are
using here seems to be, "this is how we always done it"; just like many
other defined PSR's, which leads to a conserved coding standard that
ultimately
I think it's a good idea. following..
--
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 th
>
> That's just replacing a suffix with a prefix. Zero sum game.
>
@Woody, thanks for your response. I understand that you don't see the
difference in describing the request as what sort of Request it is. Correct
me if I misunderstood you. I will try to explain why there is a difference
to me.
Le
@Woody | It depends on what type of request it is. The implementation IMO
could be called `HttpRequest`. But others may have internal and external
requests.. eg. InternalRequest and ExternalRequest.
@Daniel Plainview | No, I'm saying the same thing as you :-) it's not good
that the naming conve
@Daniel Plainview | thanks for your feedback, but I don't know if you
skipped the whole message I typed after the initial sentence. What you
describe is my conclusion as well. Please see my TL;DR:
*- Suffixes like `Interface` adds redundant noise to the code.*
*- Using the suffix makes it more c
I had this discussion with some people from room 11. The general opinion to
me seem to be *not* to use the interface suffix, so I started looking at
why. I'm all in favor for noise reduction in my code, but couldn't really
see any solution to the conflicting name conventions I faced. Someone
po
@Alessandro Pellizzari
*"So, we either put a hard limit of one message per day per person
(effectively killing technical legitimate discussions), or we selectively
and arbitrarily silence people (with possibly rising malcontent because on
injustices and "too much power on someone's hand") or we dea
Will attempt to explain my self a little before I self throat.
> Erik:
>
> On Friday, July 1, 2016 at 10:02:17 AM UTC+1, Erik Landvall wrote:
>>
>> if I where Paul, I wouldn't respond neither. There is nothing for him to
>> defend. He is who he is, it's up to
if I where Paul, I wouldn't respond neither. There is nothing for him to
defend. He is who he is, it's up to the community to welcome him the way he
is, or exclude him for that very reason.
Paul knows what he's talking about, and he is passionate about this
project. The fact that some personal
10 matches
Mail list logo
