Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104906 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 28085 invoked from network); 24 Mar 2019 00:17:05 -0000 Received: from unknown (HELO mail-oi1-f172.google.com) (209.85.167.172) by pb1.pair.com with SMTP; 24 Mar 2019 00:17:05 -0000 Received: by mail-oi1-f172.google.com with SMTP id u12so4266339oiv.1 for ; Sat, 23 Mar 2019 14:09:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=pqu5BaExMEnl1CcmM8tHKDJ2TW4xVYijRiMfYGx0ft0=; b=pYFsMGsRLDPD+8K443r25ZSipjxKxT6+blSG/MneHt9AM6gmJGgR8L3MTlAPSAhxBA dTZunOnZHO39wNSvZRhiNq/fAoLpNQitV1wDTLtr0NJUHHyIlgsOXs4gsVTJQ206fDyY 1zmGPOI4DEhp6jFkR94UBdX3/mTTE10bnMDqfuvialDKX41OHdmXlO5nn/SPBM+RBGcq fXRlSTHAoCOOEDUKdAo0VmOdyVwOg55xoEtzvqJ5bbk38J/RDH6xT5Nk8aEqJeXb5VjS p2AvQSiVo/JwXl4D8CpZ6JrjNvP4JY1nDlvLIvIZwwaIkTLDH8Ri/llbGWqQJwKcoJK3 M85g== X-Gm-Message-State: APjAAAUy0ZdJmh6joQ+3PeU9Ai8lusNAZPW41NiSl0C4jIlKitZhH8C9 T9U9oGbCvpaw7fsV36D/6ioYHavph5UMEy7bodotUrBqljM= X-Google-Smtp-Source: APXvYqxXn2w532mtT+bkyJiHxA1EmE0OHrXzStP14Rgyt+RLanII3tiGNIBwLTacjhv83QS0097Nd8n7NO1zEoleZMY= X-Received: by 2002:a54:4e02:: with SMTP id a2mr6690768oiy.140.1553375388869; Sat, 23 Mar 2019 14:09:48 -0700 (PDT) MIME-Version: 1.0 References: <33dee569-a06f-c5ab-d358-f7b8df3f8a76@lsces.co.uk> In-Reply-To: <33dee569-a06f-c5ab-d358-f7b8df3f8a76@lsces.co.uk> Date: Sat, 23 Mar 2019 23:09:35 +0200 Message-ID: To: Lester Caine Cc: Internals Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [RFC] Unbundle ext/interbase From: kalle@php.net (Kalle Sommer Nielsen) Den l=C3=B8r. 23. mar. 2019 kl. 22.59 skrev Lester Caine : > So is there anything else which is required to bring the extension up to > date? There is nothing above that prevents the extension doing it's job > for the vast majority of users and even the suggestion that it is > unusable due to Bug 72175 does not stand up to scrutiny and can now be > fixed in 7.3 and 7.2 anyway ... I updated the RFC with a section earlier to list some of the issues the extension currently has. Like Joe said in the other thread, it does bad bad things in ZTS among some of the serious issues. Even if these things are fixed, we do not have a guarantee to have someone who is capable of dealing with the issues at hand in the future, nor do I see fixing bug#72175 as a reason to halt this RFC. Like I have expressed to people who has mailed me off list (which is inappropriate) that the extension can be taken over by anyone who wants to from the relevant community, it just will not be distributed by default with PHP. In fact if the extension is released on PECL, it gives the relevant community more freedom to deal with the extension as they deem fit and does not have the strict requirements as extensions in the Core has. Sources and binaries are still available with the PECL interface. --=20 regards, Kalle Sommer Nielsen kalle@php.net