Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96276 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 65052 invoked from network); 6 Oct 2016 18:10:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Oct 2016 18:10:45 -0000 Authentication-Results: pb1.pair.com header.from=dave@mudsite.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=dave@mudsite.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.215.53 as permitted sender) X-PHP-List-Original-Sender: dave@mudsite.com X-Host-Fingerprint: 209.85.215.53 mail-lf0-f53.google.com Received: from [209.85.215.53] ([209.85.215.53:34830] helo=mail-lf0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8C/12-23443-4A396F75 for ; Thu, 06 Oct 2016 14:10:45 -0400 Received: by mail-lf0-f53.google.com with SMTP id l131so23585571lfl.2 for ; Thu, 06 Oct 2016 11:10:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mudsite-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=UoZX8oDpzWTju6S3rssxf505rzrCJn/en45Tb0NQSKk=; b=XImngDqs6+RJ6E1LP/ds8g4syz2WomLxP17qiXcH+DqDnTayE5D00dZUP7NFeSE0QH rYhM8gRly5sd4v1QIBhGLAWT0OK+tL9jQryCcWGqDtnfZMcwwicTTSEAYJly6Y13dywo 252oM4NUsnoblxE2Fs+oQkuia1t93jc5sV0hI4IgOJEXLo5vVcNKjkY26tuJuVOEtc2N Th2Cy5a4IFcaFbCRWSHxUeaFzmG2bNn2OcIueb7FYql6iaSmIZ2h5mqUC3dW5wHRHW3A hNhhFUiUpiuNL3whMBEoMs2qSJa2dwUaitfOkbDsiKPWd17gEv2bdUvCchw/q7mJ1pwP jE6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=UoZX8oDpzWTju6S3rssxf505rzrCJn/en45Tb0NQSKk=; b=G3Begn4TX4rV4q1Si/74DAMgI4819gjXSn9mQF3k4VR4xbHHLyhJgL+Sq692lBNmsw sylUD5u1dsrFapzmQrfv408IkTTZM7R6yVuBmVrF3XcBVQMfy3fR5zpJykeGYQxIfZ5G AETfj0bW8E2qf+lmO4IDoWFDhZgHtd7LN4Haooy2lu54RIZmnkYfZXLloHweYAKamjMp NttLgR9hwdD/yThEBrzJDdUdJJ1oQ1ms3lgd2hVZJj/+68ihvr0Y0TQS/4QWcH8vBE1y 1Bpu2OAXs0FYPD8ASgghx+8/PiuU1WN92hYOan9HhiOYOmBKQdzvcOZQVgbyNRxToPYq //HA== X-Gm-Message-State: AA6/9RkCQsRWnNGsQhmU/XmSpOTFo5wFstZ7SKcXffYXI9P/CGXuS1XItKenf9raT659H4o/xlMZp0FkV1LIYw== X-Received: by 10.46.32.28 with SMTP id g28mr7009075ljg.37.1475777440895; Thu, 06 Oct 2016 11:10:40 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Thu, 06 Oct 2016 18:10:30 +0000 Message-ID: To: "Christoph M. Becker" , PHP internals Content-Type: multipart/alternative; boundary=001a1142b63621efcb053e363646 Subject: Re: [RFC] Bug #72811 - Replacing parse_url() From: dave@mudsite.com (David Walker) --001a1142b63621efcb053e363646 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Oct 6, 2016 at 11:19 AM Christoph M. Becker wrote: So, I basically see two options: * wait until PHP 8 (whenever that'll be released) and switch the implementation of parse_url() then =E2=80=93 what might delay the adopt= ion of PHP 8 * add a new function in PHP 7.2 (maybe called parse_uri()), and perhaps deprecate parse_url() at the same time I'd probably side more with the former, but as a hybrid? As a stickler for naming parse_url() also seems to parses URN's correctly. imo, the proper name would be parse_uri() for something that can correctly parse any URI per the RFC. Would it be plausible to blend the options by [sorry if this is a faux pas I'm not familiar with yet] * PHP 7.2+ * Adding parse_uri() as the new RFC compliant parser * Deprecating the functionality of parse_url() with notice that parser will change to that of parse_uri() * PHP 8.0 * Alias parse_url() to be parse_uri() * Deprecate parse_url() for the name (or just let it exist as a alias forever) Obviously having two UR* parsers for the long-term would be a poor option, this might enable people to migrate to the new name & parser, before PHP 8 becomes a reality. -- Dave --001a1142b63621efcb053e363646--