Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:88166 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11031 invoked from network); 12 Sep 2015 15:57:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2015 15:57:43 -0000 Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:55642] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/60-06745-57B44F55 for ; Sat, 12 Sep 2015 11:57:42 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id 6AB696D20CA; Sat, 12 Sep 2015 17:57:38 +0200 (CEST) Received: from w530phpdev (p579F36E8.dip0.t-ipconnect.de [87.159.54.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id 0552B6D20C9; Sat, 12 Sep 2015 17:57:34 +0200 (CEST) To: =?UTF-8?Q?'Fran=C3=A7ois_Laupretre'?= , "'PHP internals'" Cc: "'Ferenc Kovacs ; Anthony Ferrara'" References: <55EE1293.7020404@php.net> In-Reply-To: <55EE1293.7020404@php.net> Date: Sat, 12 Sep 2015 17:57:37 +0200 Message-ID: <00d101d0ed73$c154b380$43fe1a80$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQH/eNXt+bKgKSdPJsSFm9R58HItZZ3b7ZZA Content-Language: en-us Subject: RE: [PHP-DEV] strict-api - Proposing a tool to check and enforce encapsulation From: anatol.php@belski.net ("Anatol Belski") Hi Francois, > -----Original Message----- > From: Fran=C3=A7ois Laupretre [mailto:francois@php.net] > Sent: Tuesday, September 8, 2015 12:41 AM > To: PHP internals > Cc: Ferenc Kovacs ; Anthony Ferrara > > Subject: [PHP-DEV] strict-api - Proposing a tool to check and enforce > encapsulation >=20 > Hi, >=20 > I have written a follow-up to my previous 'zstrict' PR. It is now = focused on a > simple mechanism to detect API violations : >=20 > https://github.com/php/php-src/pull/1508 >=20 > This version just implements the mechanism and applies it to the = zend_string > val/len/h elements. More details in the PR. >=20 > Please comment first. Then, when we're OK on the feature, we may talk = about > the target version. >=20 Personally I'd be voting yes on the principle. However as the topic = brought controversial opinions in the past, IMHO it is better to solve = it through an RFC. Especially when the idea expands over zend_string API = later, evermore devs and code will be forced by the rules, so it is = essential to ensure the majority wants it in first place. And, I = wouldn't hurry it into 7.0. Regards Anatol