Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76201
Return-Path: <lonny@lonnylot.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 56428 invoked from network); 27 Jul 2014 18:17:25 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 27 Jul 2014 18:17:25 -0000
Authentication-Results: pb1.pair.com header.from=lonny@lonnylot.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=lonny@lonnylot.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain lonnylot.com designates 209.85.192.42 as permitted sender)
X-PHP-List-Original-Sender: lonny@lonnylot.com
X-Host-Fingerprint: 209.85.192.42 mail-qg0-f42.google.com  
Received: from [209.85.192.42] ([209.85.192.42:53728] helo=mail-qg0-f42.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id EB/93-22380-33245D35 for <internals@lists.php.net>; Sun, 27 Jul 2014 14:17:24 -0400
Received: by mail-qg0-f42.google.com with SMTP id j5so7336857qga.15
        for <internals@lists.php.net>; Sun, 27 Jul 2014 11:17:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=lonnylot.com; s=google;
        h=content-type:mime-version:subject:from:in-reply-to:date:cc
         :message-id:references:to;
        bh=+MQqaVZsVrCJFK+XsJjYqrgtB2mJWg64UpII0Fe2gqc=;
        b=Pa66NqMVI4t+1yb2N8htx3JNx0xSLqBbWEoVUZW8iMCD2xDbqKykZ3xRZ4YbRc7ueu
         qDI0Z6m9VT/qsY0Fl1gd7fCACurhMtIbmZtW7B/T1ABBLQbanCMX+lA5mQZhrHtCkNVc
         HT338Gt+BnMSpvWOkzRJPhuuvsKlpsXQqtgsc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:content-type:mime-version:subject:from
         :in-reply-to:date:cc:message-id:references:to;
        bh=+MQqaVZsVrCJFK+XsJjYqrgtB2mJWg64UpII0Fe2gqc=;
        b=fIWG2W/nj81iJtRgVuT+9W0VLVTOfDA70T8Q7+ftjergky3W2VT+gSWKDHhT6KDxO9
         bSD8prc6YRiLSOlKVliIewkZ2G0ptEUZnTMc+O4/+O/JEDr35Ium+AgoOGuAs9fHx+l0
         HeF6tgNhH/X/ohe39pDXo6O9sZfkazNd14cUPvbE7zf5l5/153VOpdmWbsuUf7mrsiC2
         Y+Hl2pkFTKcM1QJI9crBhUuu1oqNP+xmPtul/ZsGj2Pv8TsSbkwJapVfNBVXFxdrWfUH
         k/kdZ/uDK9JXVxSnWtUhBOn/rp9+01aJR4yjC6D91OWrakdqcWKYF+bamWZv1tcDZYCl
         4ocA==
X-Gm-Message-State: ALoCoQlddxcwRxCRlWiBT262ROCnldwfL5tpRVwCPCq1+ByMzeDfq3e0OzkJESMZPkxzgnXB55zv
X-Received: by 10.224.137.135 with SMTP id w7mr51211025qat.52.1406485051634;
        Sun, 27 Jul 2014 11:17:31 -0700 (PDT)
Received: from [10.0.0.4] (cpe-68-174-155-165.nyc.res.rr.com. [68.174.155.165])
        by mx.google.com with ESMTPSA id w15sm24804223qay.34.2014.07.27.11.17.30
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sun, 27 Jul 2014 11:17:31 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_9E9EEC50-2F63-4CEC-8ABE-2064E4A7E4A1"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <CAEZPtU6fuofAo7yy98qj8ijymdySukd1_5YJCc=bifLF=btasA@mail.gmail.com>
Date: Sun, 27 Jul 2014 14:17:31 -0400
Cc: PHP internals <internals@lists.php.net>
Message-ID: <CB8034ED-00AA-4FCA-B368-61E579F9D0C8@lonnylot.com>
References: <482DEC36-8A5A-4840-910A-3C63CA3A503B@lonnylot.com> <B2A0452A-354A-4733-A3D7-0E8ABE61DAC6@ajf.me> <CAEZPtU7HQ5Y-h_36pTBb_2NMZfo=UEzwWKHL4k630y+Jbh7XYQ@mail.gmail.com> <77BCF83D-F7AF-4853-8C40-D07D1CFFF8DE@lonnylot.com> <CAEZPtU6fuofAo7yy98qj8ijymdySukd1_5YJCc=bifLF=btasA@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>,
 Andrea Faulds <ajf@ajf.me>
X-Mailer: Apple Mail (2.1878.6)
Subject: Re: [PHP-DEV] [RFC] imagettf* deprecation/removal
From: lonny@lonnylot.com (Lonny Kapelushnik)

--Apple-Mail=_9E9EEC50-2F63-4CEC-8ABE-2064E4A7E4A1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Jul 27, 2014, at 1:19 PM, Pierre Joye <pierre.php@gmail.com> wrote:
>=20
> However the idea to add yet other warnings/notices to ext/gd is not
> something I like to see in GD. I will rather remove many for php-next
> instead of adding more. Also some new font APIs may as well make the
> whole ttf ones less relevant, see the upstream version.

Pierre,

I would only want to add E_DEPRECATED to the function calls if we are =
actually going to remove them. Otherwise, I agree that we should not add =
it. Also, I noted it in the RFC, but want to make mention here in case =
you did not see: I=92m suggesting E_DEPRECATED in 5.6.z+1 and removal in =
php.next.

On Jul 27, 2014, at 1:22 PM, Andrea Faulds <ajf@ajf.me> wrote:
> The API signatures are compatible, yes? In which case, just make the =
legacy functions be aliases of the new ones. This avoids breaking =
everyone=92s code.

Andrea,

I don=92t think that assessment accurately reflects the situation. I=92m =
suggesting to change the userland API in php.next. According to the =
release process the whole point of a php.next is to break the API for =
improvements. Anyone upgrading to php.next is going to have to check for =
BC breaks.

I=92m suggesting having this minor change be one of the BC breaks in =
php.next. I=92m not making the argument that it is important from a =
purely technical POV; I don=92t believe it is. I=92m making the argument =
that it is important from an operational POV. Removing them prevents =
newcomers and gurus from ever having any question about which function =
to use.=

--Apple-Mail=_9E9EEC50-2F63-4CEC-8ABE-2064E4A7E4A1--