Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:68992
Return-Path: <admacedo@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 74373 invoked from network); 10 Sep 2013 15:11:35 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 10 Sep 2013 15:11:35 -0000
Authentication-Results: pb1.pair.com smtp.mail=admacedo@gmail.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=admacedo@gmail.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.172 as permitted sender)
X-PHP-List-Original-Sender: admacedo@gmail.com
X-Host-Fingerprint: 209.85.223.172 mail-ie0-f172.google.com  
Received: from [209.85.223.172] ([209.85.223.172:58635] helo=mail-ie0-f172.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 75/69-03199-6A63F225 for <internals@lists.php.net>; Tue, 10 Sep 2013 11:11:35 -0400
Received: by mail-ie0-f172.google.com with SMTP id c10so16699849ieb.3
        for <internals@lists.php.net>; Tue, 10 Sep 2013 08:11:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=KPj6fbc6vi8r+evlQGEIOdiNHSENZS+uh1+sNmQaJlY=;
        b=i01PUgsdd+bUJ+kUZGrnk8+gv1xKzAEZkuEQqajRP3nBFYZ/eT7dCqpPLTFS7Qy8rR
         4YGImYpqwoxJSeXecSz2LxJHfXqGjqXP0fjYUm1PhDDYb/6gDE84ZwQHGVrUZQCJITBY
         EbODOTw/f92FiiW9hOoqliVqkjP0E+VUfSIHt4i8n0A3N3mivWtKz0nPFcF8IqDpPRg7
         7I5yR/wfE/t5mAHQ+byke92A5eIKzr3uBQhp652lbnhzfEloR/1G1Pp1VaaTfzEL1bXd
         qL1Z+aQl+gtCdGdelkAFZVAdM9/Q/zhWjVHCNc3vJkW6nEFuAa29FMDK299yHkrou1jV
         KNqQ==
X-Received: by 10.50.77.83 with SMTP id q19mr10886392igw.21.1378825891930;
 Tue, 10 Sep 2013 08:11:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.240.77 with HTTP; Tue, 10 Sep 2013 08:10:50 -0700 (PDT)
In-Reply-To: <522EF22F.1040006@lerdorf.com>
References: <CAF+90c85v_VTPTPanBcTJ70Ff6pm6fRgAGs4n1uoaA+B9UZg=w@mail.gmail.com>
 <CAF+90c8qj_3is8Dj4XbkUwL1Y8eVCEPXVYfwhDdaabHWuGzY2Q@mail.gmail.com>
 <CA+yzxZh0H6rqf3wdzGVjGJs+iaMajgHgNqSMkq=fsiR4eZfkaA@mail.gmail.com>
 <CAF+90c_Ygb7TrDp7uv-0J4s7AVO20Z9OwkXW4XMN6DQDt3bFog@mail.gmail.com> <522EF22F.1040006@lerdorf.com>
Date: Tue, 10 Sep 2013 16:10:50 +0100
Message-ID: <CA+yzxZhtKxkZXEEuOpvFY+RPyGrzM21chcjBMY1Uupuwwe_mXA@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [PHP-DEV] Re: [RFC] Named parameters
From: admacedo@gmail.com (Daniel Macedo)

On Tue, Sep 10, 2013 at 11:19 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> I think you are over-thinking this case actually. I would prefer to just
> keep it simple. If someone does a named parameter call to a method that
> doesn't have a parameter with a specified parameter it is an error,
> regardless of how that came to be. If there is a parent method with the
> parameter name, it doesn't matter since that is not the method they are
> calling. Just keep it simple and generate an error just on that call.
> The fix for the user in this case may very well be to go and make the
> parameter names match the parent method, but let them worry about that.
>
> -Rasmus

Thanks, this makes more sense to me, and is surely a less complicated
implementation.