Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68921 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44254 invoked from network); 6 Sep 2013 19:12:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Sep 2013 19:12:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 74.125.82.175 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 74.125.82.175 mail-we0-f175.google.com Received: from [74.125.82.175] ([74.125.82.175:53692] helo=mail-we0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id F5/67-05619-2192A225 for ; Fri, 06 Sep 2013 15:12:21 -0400 Received: by mail-we0-f175.google.com with SMTP id q59so3402403wes.34 for ; Fri, 06 Sep 2013 12:12:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=8L5T82nBu0EVfLAdEt2EKL99Toy8aShZSKWceU9ROyE=; b=G0SoOxIPvWEK+8fNO0CLdExPeDsDVFPIcHWTcIpQ/1WTwjuInPh1dsE/l5otxnVL8r 50R46U0xVQyogkDLgPjVe57cpCThIziQhk0NZ3OiCJ0QbJsgjZkA1DfzINQoWth0p6J5 1ggzmKqOB3259AMR8qRcHxbQyuvQiT7VCT65AzeRhPf813TtcW6kABPhandswToiXMu3 3x9Pl03e1d+QvM0dqjqx4l7XP11Vrus6LQHuVRcwdE02OF0hVPvdErF+gTpCXMSzsbP/ x5ofkDn0zTTKiLIU4ZKmDbOkepO1RAiKl7ljYvkxiWkRZNOhCV9zIZWkoA1ousS3+zLH 2moQ== X-Gm-Message-State: ALoCoQl73iqFZo7XG9jr4QyTFPMVdSkfAbYHAlk4uO+viuO3AfmqSlpdj2sxZU+wakBQeNjr/m41 MIME-Version: 1.0 X-Received: by 10.194.109.35 with SMTP id hp3mr2651049wjb.55.1378494736437; Fri, 06 Sep 2013 12:12:16 -0700 (PDT) Received: by 10.217.10.73 with HTTP; Fri, 6 Sep 2013 12:12:16 -0700 (PDT) X-Originating-IP: [2.96.87.110] In-Reply-To: References: Date: Fri, 6 Sep 2013 20:12:16 +0100 Message-ID: To: Nikita Popov Cc: PHP internals Content-Type: multipart/alternative; boundary=089e010d85741722f304e5bbd15d Subject: Re: [PHP-DEV] [RFC] Named parameters From: danack@basereality.com (Dan Ackroyd) --089e010d85741722f304e5bbd15d Content-Type: text/plain; charset=ISO-8859-1 Hi Nikita, > If named parameters are introduced, signature validation should include > parameter names. Throwing a fatal error (for the interface/class combination) > would break backwards compatibility though. We could use some lower error > type... Would it be possible to set the error level through an ini setting? Or disable it entirely? People who are writing new code that is aware of named parameters should want a fatal error for any coding mistake that violates the contract. People who are supporting legacy code that doesn't use named parameters should be able to upgrade to the latest version of PHP without having to refactor an entire code base or suppressing huge numbers of compiler warnings. cheers Dan On Fri, Sep 6, 2013 at 5:39 PM, Nikita Popov wrote: > Hi internals! > > I created an RFC and preliminary implementation for named parameters: > > https://wiki.php.net/rfc/named_params > > The RFC and implementation are not yet complete. I mainly want to have > feedback on the idea in general and on the Open Questions ( > https://wiki.php.net/rfc/named_params#open_questions) in particular. > > Thanks, > Nikita > --089e010d85741722f304e5bbd15d--