Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60681
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+aNemY68hTDqUC7Zj7JUEZx+T4pCHWZ37wGjTLTKjUJ3fofew@mail.gmail.com>
References: <CA+aNemYeQmWXGXCa7hosh2WyBq7zWh9bmgFLrOd5V=v=-cBQsg@mail.gmail.com>
	<CA+yzxZh7aDoj8CiS82KNARf8KfLxDNhGx2Hix-H6PwXjK1d-+A@mail.gmail.com>
	<CA+aNemY68hTDqUC7Zj7JUEZx+T4pCHWZ37wGjTLTKjUJ3fofew@mail.gmail.com>
Date: Sun, 27 May 2012 18:14:17 -0700
Message-ID: <CACePOD77j=6f_N22kP+NX+7S6ycpof0P=ATneRqD58BrUcx8CA@mail.gmail.com>
To: internals@lists.php.net
Content-Type: multipart/alternative; boundary=e89a8fb1ec70e1501704c10e6f51
Subject: Re: [PHP-DEV] RFC Skipping optional parameters for functions
From: william.betts@gmail.com (William Betts)

--e89a8fb1ec70e1501704c10e6f51
Content-Type: text/plain; charset=ISO-8859-1

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.

--e89a8fb1ec70e1501704c10e6f51--