Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:100331
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CA+kxMuQuzFJvms4Xa-VV-b2pf0zSaUmTMvcVfrsh7uTGPZot3g@mail.gmail.com>
References: <CADqTB_hNm6ceRVyW9698_3v1qEtXC=uDLhiVzVcJ5y92aJTO+A@mail.gmail.com>
 <CAJW__o1N4zSYgRGOg7jxS8oA6FANGLV2zqE_PvvXUKgktX0JWQ@mail.gmail.com> <CA+kxMuQuzFJvms4Xa-VV-b2pf0zSaUmTMvcVfrsh7uTGPZot3g@mail.gmail.com>
Date: Wed, 30 Aug 2017 18:30:36 -0700
Message-ID: <CAKOpQSyubNQp+gJcpwp9gaUL9+gp2xvbSTqMFEo=gzsWyLKONQ@mail.gmail.com>
To: Dan Ackroyd <danack@basereality.com>
Cc: Rasmus Schultz <rasmus@mindplay.dk>, PHP internals list <internals@lists.php.net>, 
	Kalle Sommer Nielsen <kalle@php.net>
Content-Type: multipart/alternative; boundary="001a11409334770262055802974e"
Subject: Re: [PHP-DEV] GD vs Imagick
From: kris.craig@gmail.com (Kris Craig)

--001a11409334770262055802974e
Content-Type: text/plain; charset="UTF-8"

2. Releasing Imagick with PHP means that the release cycles would need

to be sync'ed. This has proven to be inconvenient in the past when an
extension has wanted to change the api, but was forced to wait due to
needed to wait for the next minor/major version of PHP.


Why would they need to be synced?  When PHP releases a new version, can't
we just bundle the latest Imagick build and plug into that?

Sure, having them in sync would yield certain benefits, but none of them
appear to be deal-breakers to me.  Or am I just missing something?

--Kris

--001a11409334770262055802974e--