Re: Proposal for extended coding style guide

I also use the second case. Should we open a poll for that ? Or was it covered in the survey that were done a long time ago ? and by the way were that survey result ever published ? -- You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability

Re: [VOTE][CC] Entrance vote for PSR-12: Extended Coding Style Guide

+1 Phergie On Fri, Oct 20, 2017 at 5:30 PM, Larry Garfield wrote: > +1 > > --Larry Garfield > > > On 10/19/2017 01:39 PM, Korvin Szanto wrote: > > Hi Everyone, > PSR-12 was already accepted and assigned the number 12 back in FIG 2.0[0], > however, it turns out that my

Re: [VOTE] Secretary Election

1. Margret Staples 2. Mark Railton 3. Alessandro Lai Good Luck and Godspeed Secretaries :D - Phergie On Mon, Oct 23, 2017 at 4:06 PM, GeeH wrote: > 1. Margret Staples > 2. Mark Railton > 3. Alessandro Lai > > > G > > -- > You received this message because you are subscribed to

Re: [VOTE] Secretary Election

1. Margret Staples 2. Mark Railton 3. Alessandro Lai G -- 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

Re: [VOTE][Entrance] Extended Coding Style Guide

+1 from Phing Am Montag, 24. August 2015 18:37:02 UTC+2 schrieb Korvin Szanto: > > PHP 7 is coming out soon with some new features like return types[1] and > uniform variable syntax[2]. We hope to put together a solid agreeable PSR-2 > extended recommendation for syntax changes made past php

Re: Proposal for extended coding style guide

Type casting and syntax "hacks" (eg: to call a closure assigned as a property) are very different and not comparable, IMO. My personal preference would be: $foo = (int) $foo; and return ($this->callback)(); // or return call_user_func($this->callback); -- Woody Gilk http://about.me/shadowhand

Re: Proposal for extended coding style guide

I’ve always used the first case. Consider another similar situation: calling a callable that’s also a property of self. You’d have to call it with parentheses — that is, ($callback)(); with no spaces. I feel like the first case is more consistent when taking into account the rest of the

Re: Proposal for extended coding style guide

I've always used the second case. The first feels really cramped IMO. On Mon, Oct 23, 2017, 04:47 'Alexander Makarov' via PHP Framework Interoperability Group wrote: > Same here. Using 1st case. > > > On Monday, October 23, 2017 at 12:28:17 PM UTC+3, Alessandro Lai

Re: [VOTE] Secretary Election

1. Margaret Staples 2. Alessandro Lai 3. Mark Railton > On 19 Oct 2017, at 23:17, Michael Cullum wrote: > > Hi all, > > We've been attempting to get more nominations so this has been delayed a few > times but we now have three candidates so we're rolling with it. > >

Re: Proposal for extended coding style guide

Same here. Using 1st case. On Monday, October 23, 2017 at 12:28:17 PM UTC+3, Alessandro Lai wrote: > > This is an interesting topic. I've always found inconsistencies on this > topic, since some formatters use the first case, others the latter. > > I'm inclined for the first case, since it's

Re: Proposal for extended coding style guide

This is an interesting topic. I've always found inconsistencies on this topic, since some formatters use the first case, others the latter. I'm inclined for the first case, since it's normally applied just to the symbol at the immediate right of it... Il giorno lunedì 23 ottobre 2017 08:56:35

Proposal for extended coding style guide

Hello Could you please add typecasting space issue in https://github.com/php-fig/fig-standards/blob/master/proposed/extended-coding-style-guide.md ? $intValue = (int)$stringValue; or $intValue = (int) $stringValue; Thank you -- You received this message because you are subscribed to