Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76196
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 47444 invoked from network); 27 Jul 2014 17:09:18 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 27 Jul 2014 17:09:18 -0000
Authentication-Results: pb1.pair.com smtp.mail=lonny@lonnylot.com; spf=pass; sender-id=pass
Authentication-Results: pb1.pair.com header.from=lonny@lonnylot.com; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain lonnylot.com designates 209.85.192.51 as permitted sender)
X-PHP-List-Original-Sender: lonny@lonnylot.com
X-Host-Fingerprint: 209.85.192.51 mail-qg0-f51.google.com  
Received: from [209.85.192.51] ([209.85.192.51:61845] helo=mail-qg0-f51.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id EF/D1-22380-D3235D35 for <internals@lists.php.net>; Sun, 27 Jul 2014 13:09:17 -0400
Received: by mail-qg0-f51.google.com with SMTP id a108so7290631qge.24
        for <internals@lists.php.net>; Sun, 27 Jul 2014 10:09:25 -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
         :content-transfer-encoding:message-id:references:to;
        bh=Q7k3Q2dpAR7tXwe8h+OR/FcE2LfFUjJXKZ8hyHzTI/I=;
        b=jKKqjJMNcFhhHWAvvZqXKFmlrqCEMvi42hFfF8lDR44cPQaw0vks/J4Wq3QXuBls+4
         rstm0ks4Kycnt5DI7ISj3Z5XHH5QK4Sz0o1ReuUj34M+YFbe4v52Bg/Q7S5GvD9p2gH1
         JR1tCdPwm8D0kTdNHIXuFgOlx6td3nCw4ox/w=
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:content-transfer-encoding:message-id:references
         :to;
        bh=Q7k3Q2dpAR7tXwe8h+OR/FcE2LfFUjJXKZ8hyHzTI/I=;
        b=DYnKoPvoP363oXml7xHp72Af1IhqG59nwNqO6cy46QT6732PryQV3V7x7OO9IJcbZl
         UXAK0uI4C4KzuweUISS4iHX+lZcF/B5wGNxyobNV90z7x7+CVuTYu3vVi7xwl+fLqWFd
         wli7XKOW0px4EON9J8tuJPXVEyTnLKCcsxTDES1XwWmYYboHZwmZgLCxBH6jJNgHj3jE
         bXUhYpOkMWGxUDXJPBS74DIkaFc9NkMOJwGkAPLymhk6tzX4qIxJyU6aWu0t4jF92PkN
         ZvtXddhkV5QNlDXWqQqYR7P53fEM+UKeFCyC4C1vEq7pYMwmtK9NjDYlzXNsCVPSFNPm
         vAAw==
X-Gm-Message-State: ALoCoQnVC9oXbyfyRnTIUno0xO7WA3SmVrHNNrBbotYk7CsbZet0n5EqdOoQGNxAkzGV+IhOCwXa
X-Received: by 10.224.65.73 with SMTP id h9mr50646150qai.83.1406480965195;
        Sun, 27 Jul 2014 10:09:25 -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 33sm19283898qgt.28.2014.07.27.10.09.24
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sun, 27 Jul 2014 10:09:24 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
In-Reply-To: <CAEZPtU7HQ5Y-h_36pTBb_2NMZfo=UEzwWKHL4k630y+Jbh7XYQ@mail.gmail.com>
Date: Sun, 27 Jul 2014 13:09:24 -0400
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <77BCF83D-F7AF-4853-8C40-D07D1CFFF8DE@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>
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)


>> Wouldn=92t it be simpler to just make them aliases?
>=20
> Indeed, and as I have no problem if  Lonny likes to go ahead with this
> RFC, I do not think we need one for such trivial change.


Andrea,

Whom are you suggesting the alias would be simpler for?

Personally, I do not think it would be simpler for the userland API to =
have them aliased. I think an alias will cause unneeded confusion, =
discussions, and waste time in an office.

Pierre,

The idea behind making this an RFC is to come to an agreement on both =
the change and the timeline now so there are little/no questions later.