Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:105927 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 81176 invoked from network); 14 Jun 2019 18:14:50 -0000 Received: from unknown (HELO mail-qk1-f174.google.com) (209.85.222.174) by pb1.pair.com with SMTP; 14 Jun 2019 18:14:50 -0000 Received: by mail-qk1-f174.google.com with SMTP id x18so1882693qkn.13 for ; Fri, 14 Jun 2019 08:28:16 -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:reply-to :from:date:message-id:subject:to:cc; bh=OpEG8hzvTFaQwrKz1RvVUtmdf1MTvS87HtMOWgGPis4=; b=LPE4m/kmJcJFOjlI+xeU6YYPe4AkKpcR/7uK+mOx6GXD5WzEloLlQ9m3Ansyvo8Tpa Jz3Q3AhkQ2w1k+Q9vmpKkoPXRYzcNcW8W/qMc4GQa7SguVO/gK2P/Abu3UzNAXYKDzEz GFh4GT6qTBFMt47isdiMBi5YxSga6pqPnMMvaE4b2QvIQ5JpB43vvWYN9P4+idp40UO4 wIG4PXvvqx3/wO8pk525s68bWjEh2h3r4DBqU/AVEJmLpgRispfEliNRH+ub3R1+Lsqr aml5wtLGc/zapNsImvSywWwNUL1ZaT8JFWDUP5REnBimJowRAf/2/AhdKlP2EWDZBnt/ zgnA== X-Gm-Message-State: APjAAAUyYZkW53+udUvESUz3TtlqYFIXSridBIKJ2O+2cHwecljDSqrB TZlp4J5YxVuLX1eQRLVzwclW1nea2SrZU5g12uQ= X-Google-Smtp-Source: APXvYqy3fyXdQ4o0IJOAUEv3MOm+ICNUlIFDlkvmX5GZu79LQhyF1qjhvawtO2Bznp3xOAkVkEPR+L46T+nkmtafc28= X-Received: by 2002:a05:620a:15d3:: with SMTP id o19mr57374300qkm.213.1560526095799; Fri, 14 Jun 2019 08:28:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Reply-To: bishop@php.net Date: Fri, 14 Jun 2019 11:27:50 -0400 Message-ID: To: "G. P. B." Cc: PHP internals Content-Type: multipart/alternative; boundary="0000000000009a583d058b4a4b03" Subject: Re: [PHP-DEV] Feedback on state of some PHP extensions, functions, etc. From: bishop@php.net (Bishop Bettini) --0000000000009a583d058b4a4b03 Content-Type: text/plain; charset="UTF-8" On Fri, Jun 14, 2019 at 8:15 AM G. P. B. wrote: > On Wed, 12 Jun 2019 at 18:16, Bishop Bettini wrote: > > > On Wed, Jun 12, 2019 at 11:35 AM G. P. B. > > wrote: > > > >> - PharData::setAlias, PharData::setDefaultStub and PharData::setStub > >> always throw PharException > >> [11] [12] > [13] > >> [11] https://www.php.net/manual/en/phardata.setalias.php > >> [12] https://www.php.net/manual/en/phardata.setdefaultstub.php > >> [13] https://www.php.net/manual/en/phardata.setstub.php > > > > > > I don't know how much this is used in the wild, but these methods exist > so > > that a user may treat a Phar and a PharData as interface-equivalent > objects > > independent of the phar.readonly INI setting. I lean toward leaving these > > no-op methods as is, but I am happy to further discuss their merit. > > > > This does make sense, liek said I was just going thought the doc and didn't > try to see the bigger picture especially as I don't use Phar at all. > Would it make sense to create an interface PharStream (or something else) > on which both these object inherit? If this doesn't make sense please > ignore me. > Sure, possibly. I've added this conversation to the related PHP Bug #69196 https://bugs.php.net/bug.php?id=69196 --0000000000009a583d058b4a4b03--