Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:68922 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 45774 invoked from network); 6 Sep 2013 19:16:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Sep 2013 19:16:34 -0000 Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.223.171 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.223.171 mail-ie0-f171.google.com Received: from [209.85.223.171] ([209.85.223.171:52875] helo=mail-ie0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/B7-05619-01A2A225 for ; Fri, 06 Sep 2013 15:16:32 -0400 Received: by mail-ie0-f171.google.com with SMTP id 9so7930315iec.30 for ; Fri, 06 Sep 2013 12:16:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=VdFF3u6Sa16PFcH4FieMRjJAkovw3G43oSCDSPVIcYo=; b=QcxiMhuJEShH4hnk/O8FaHBUzlVkbta+ZPF06Q5p9kb/VwGTCxiDME7YINMMFAhEHQ ys3K6/CLMij41522yneXSA4mP1vMrrPOb9119CwS5N+vrUsVyRhGs6fsKtz6jR+RrlwN ut5GrFjgVmgddkI3/HKYSHk/gorefcr66xakM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=VdFF3u6Sa16PFcH4FieMRjJAkovw3G43oSCDSPVIcYo=; b=Z8K8oFuR+LfwXskLRY6uZTIXslVp0eDjeas5uWm65ub+SsIu/s0OCbB9Mw7H+yw7UC aLzds6TyXkT4yL1JXZ7gJ9I/un5NSEl6Bw5Kq7gzO3nU8AYvgFIp26FznnWBrx+WMLQk /LNSgYE18hDC3mG9/E+0Rfafi1XYLrm9FXnEWRKHyQY5WKNMLEXlrre79XwmDRbDARO1 ocVLwQ/jcHWtrzJ08Z9FkQufZgifGJrz3kV65BlCLBBkfRRJsV+W7HWLFsXl0Ruu4A/N LuopddwDc2BLEoXf1S2lDuJb/INDWYo2zVPN/Fat1GgjhVih/wfnkxKhpUlPma9/G8e6 hQaw== X-Gm-Message-State: ALoCoQl+GTwyClYdhCFFVROMbHDIJNZqXzgbZMTPOmzTVti64P6Ol65qu7TJCD2oGllzfNUZd15z X-Received: by 10.42.60.18 with SMTP id o18mr13391ich.83.1378494989800; Fri, 06 Sep 2013 12:16:29 -0700 (PDT) MIME-Version: 1.0 Sender: adam@adamharvey.name Received: by 10.42.206.208 with HTTP; Fri, 6 Sep 2013 12:16:09 -0700 (PDT) In-Reply-To: References: Date: Fri, 6 Sep 2013 12:16:09 -0700 X-Google-Sender-Auth: Q6l083t7Q6ARV2QERAbfj6j2UgU Message-ID: To: Dan Ackroyd Cc: Nikita Popov , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Named parameters From: aharvey@php.net (Adam Harvey) On 6 September 2013 12:12, Dan Ackroyd wrote: >> 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 erro= r >> type... > > Would it be possible to set the error level through an ini setting? Or > disable it entirely? I've said this before, but to reiterate it: I'd be a huge -1 on anything that involves configurable language behaviour. It's a support nightmare, and I'm glad those days are now mostly over. > 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. I'd say the odds are that those sorts of users are going to be writing code that is required to be notice/strict clean anyway =E2=80=94 that's certainly been true everywhere I've worked that's had a "modern" codebase. Adam