@Stefano
> this comes down to personal preference
Much like everything in PSR1 and PSR2 that addresses format, position of
curly braces and indention. The only difference being, that there's an
actually argument for why a prefixed definition would have a bad impact,
while a different indentation an
>
> @Stefano
> > This is a non issue...
> This is important for a standard, others are adopting to what you do here
> - that's the definition of a standard. Coders sees and copies what you do
> and even use it as an argument when discussing the issue, it's natural for
> this discussion to show up i
@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
