Re: RFC Skipping optional parameters for functions
| From: | William Betts | Date: | Mon, 28 May 2012 01:14:17 +0000 |
| Subject: | Re: RFC Skipping optional parameters for functions | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-60681@lists.php.net to get a copy of this message | ||
On Sun, May 27, 2012 at 11:28 AM, Mathias Grimm <mathiasgrimm@gmail.com>wrote:
> Named parameter in the same way that goto does, with labels. A labeled
> parameter...
> But there always some drawbacks... such as mix named and conventional
> parameters. I think that you just chose one way and use, not allowing mix
> these two ways.
>
> <?php
> goto a;
> echo 'Foo';
>
> a:
> echo 'Bar';
> ?>
>
>
> I also think that should exists a strict way to write code, something like
> error_reporting, but to ensure a specific way to write code, gaining speed
> in the whole compilation thing.
>
> strict_code_standard = K&R
> strict_code_standard = GNU
> strict_code_standard = PEAR
> strict_code_standard = ZEND
>
> The GO land does it in some way
>
I can see how enforcing a strict coding standard would be useful, but only
if you're also allowed to define your own.