On Thursday, 9 March 2017 22:40:08 UTC, Marco Perone wrote:
>
> ...
>
> More broadly, could it be the case to provice a precise definition of what
> StudlyCaps mean? (If it's not present elsewhere and I'm missing it...)
>
I'm wondering whether this is a term we should be even using? It seems
t
Hi Marco,
On Fri, Mar 10, 2017 at 9:25 AM, Marco Perone wrote:
> Hi Paul, thanks for your answer,
>
> I know that the final underscore is not passing the PSR-1 codesniffer
> test. That's where I started from (https://github.com/squizlabs/
> PHP_CodeSniffer/issues/1382). I was more wondering if t
Hi Paul, thanks for your answer,
I know that the final underscore is not passing the PSR-1 codesniffer test.
That's where I started from (
https://github.com/squizlabs/PHP_CodeSniffer/issues/1382). I was more
wondering if that is the correct approach.
I agree it should be generally avoided to nam
Hi Marco,
Comments inline.
On Thu, Mar 9, 2017 at 10:40 PM, Marco Perone wrote:
> As per PSR-1 specifications, class names must be in StudlyCaps.
>
>
> However, if I want to define a class named Echo (or any other Php
> keyword), I am not able to do that beacuse if I do so I obtain a parse
> er
As per PSR-1 specifications, class names must be in StudlyCaps.
However, if I want to define a class named Echo (or any other Php keyword),
I am not able to do that beacuse if I do so I obtain a parse error.
It seems that the standard solution to this issue is to add an _ at the end
of the