Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:88167
Return-Path: <kalle.php@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 13379 invoked from network); 12 Sep 2015 16:22:26 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 12 Sep 2015 16:22:26 -0000
Authentication-Results: pb1.pair.com header.from=kalle.php@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=kalle.php@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.177 as permitted sender)
X-PHP-List-Original-Sender: kalle.php@gmail.com
X-Host-Fingerprint: 209.85.212.177 mail-wi0-f177.google.com  
Received: from [209.85.212.177] ([209.85.212.177:36356] helo=mail-wi0-f177.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id E6/D0-06745-F3154F55 for <internals@lists.php.net>; Sat, 12 Sep 2015 12:22:25 -0400
Received: by wicgb1 with SMTP id gb1so94273945wic.1
        for <internals@lists.php.net>; Sat, 12 Sep 2015 09:22:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date:message-id:subject
         :from:to:cc:content-type:content-transfer-encoding;
        bh=qj5cZgt9Mbu5rNV8AeQluK7GSLaVBuX/pLzY6nuZTvg=;
        b=jZjNlpyQF3bdLUFyr9iQ3Ls7X7WGhVxSzsxDaHSJEbP4P+dw19fmymP/zwP1uZOEqe
         7FFY2xSNqnrkFZCla+z+eAL9WGuyJYUtz5DIoNTkU7ju3XkiKIG6jj9wfZKBDQcUjOjz
         tkZ0Ga9ljoSJrkdF84PfjvunDGPWyBsnebptPv69iuoJPOoTLVnUMUl7ZmbXg7QYZkQa
         soJx723dGyGQ83VEgFYW/n0U+UF+mIzBobE+kEmkJK4gyOxia9qZlv8rnnDHjrQ0+8Ll
         j+oBYodyFswQz23d7FJ56ian79oOtj9Kqf3Zdi87y/ugKkQrJjjwbYvcq/o1X0mKov8t
         eRTQ==
MIME-Version: 1.0
X-Received: by 10.180.103.167 with SMTP id fx7mr7415335wib.89.1442074940458;
 Sat, 12 Sep 2015 09:22:20 -0700 (PDT)
Sender: kalle.php@gmail.com
Received: by 10.28.128.204 with HTTP; Sat, 12 Sep 2015 09:22:20 -0700 (PDT)
In-Reply-To: <00d101d0ed73$c154b380$43fe1a80$@belski.net>
References: <55EE1293.7020404@php.net>
	<00d101d0ed73$c154b380$43fe1a80$@belski.net>
Date: Sat, 12 Sep 2015 18:22:20 +0200
X-Google-Sender-Auth: WOBUlv6t1iYWk4VCXt9_re6k9Vo
Message-ID: <CAJW__o2rUCmf5mtNxYVWtvp+2qKt5C2f3s93iD-0kFEusiG8Yw@mail.gmail.com>
To: Anatol Belski <anatol.php@belski.net>
Cc: =?UTF-8?Q?Fran=C3=A7ois_Laupretre?= <francois@php.net>, 
	PHP internals <internals@lists.php.net>, 
	"Ferenc Kovacs <tyra3l@gmail.com>, Anthony Ferrara" <ircmaxell@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] strict-api - Proposing a tool to check and enforce encapsulation
From: kalle@php.net (Kalle Sommer Nielsen)

Hi

2015-09-12 17:57 GMT+02:00 Anatol Belski <anatol.php@belski.net>:
> Personally I'd be voting yes on the principle. However as the topic broug=
ht controversial opinions in the past, IMHO it is better to solve it throug=
h an RFC. Especially when the idea expands over zend_string API later, ever=
more devs and code will be forced by the rules, so it is essential to ensur=
e the majority wants it in first place. And, I wouldn't hurry it into 7.0.

I agre, but I don't see any chance of this making it into the 7.0
branch at current state, so I would recommed targetting 7.1 at
earliest


--=20
regards,

Kalle Sommer Nielsen
kalle@php.net