Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:104069 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 65497 invoked from network); 3 Feb 2019 21:11:40 -0000 Received: from unknown (HELO mail-wr1-f42.google.com) (209.85.221.42) by pb1.pair.com with SMTP; 3 Feb 2019 21:11:40 -0000 Received: by mail-wr1-f42.google.com with SMTP id r2so403633wrv.10 for ; Sun, 03 Feb 2019 09:52:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Nk55nYg63sQMNl4z+k2kf9OLrJ2ZkskDtrQTFk319lE=; b=F+D3ZmDv6FNUZGumOwmwdhJiJ8kVQn1IlPPWuhuQ6LmUc5NjijB+LAS9QOAyK9ZydL gLn6hHd4kGrO2xAwZeS7hsh7Frrpwx7OyCylbVZeDPIL+XRui8IY+Q8hMmAnTAIEDg5J SdbL8FCWuWXlZy4GklH1HfuM/JxxezYrZ2MRIBR84i5FrMM+58/ukDvtyGhlE35cSslU X7rbkStjxBYSWv/qEXCn0+saQ1lY9OTy661R9V8ebXx+thH/BVsIZ3K8bDdbRH1z0XBC KEc5hpJc3HSmYx034aqlrXme4irsFn9et0UZWiGCGzmrHC6aqRyXjE2E4UWXdD7/HqwE zteg== 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; bh=Nk55nYg63sQMNl4z+k2kf9OLrJ2ZkskDtrQTFk319lE=; b=WqXzaGwW6igk/3WXI1C6KTPc8+Q7i0go+cTsxyPsuSBPymt6Nupv+jqEHC5ZO/tysy ZMm/vaqkjIsroUKRL/aHRVS/rYEg2Cubv6crodNiTuR3w8RdniBN1c5RkB3mzllCc8Up PWKvFG2PicpsKXf7PyrsQTRXdQ0J8gbIcr6ZS7OOKGLOvNVHD0CbBef6zYAyu4mk33Jw PY7VbUv/9EPUIuU8syKCLaOxT/3p/NPK/YaNRvGant+PAjlP8ZwaayXWaTJULeMSpzJH /jZTJ5n+FR3OZXS+HylmM6iTYrMBB1Ahl/nSQQyk18QAO6hkJNkvloLWPL4dR7p9rgXb q9kQ== X-Gm-Message-State: AHQUAua9csRqrK9LZDC3fngchx+D8ZzcpejbGl6uxXVdgxR5Zoe4KBBL h/Pqy+j1Wdaek8tiSxOB/D5Zexj4nK6n9vky73Y= X-Google-Smtp-Source: AHgI3IaZNQj3Nc0K/IDamdVmyBMEleRVijZ4co7p0rPWmxeoZsygbzV9EPNatafzLuXSqVYRL+uXbiaJzNrogZc64cM= X-Received: by 2002:a5d:6487:: with SMTP id r7mr6613449wru.263.1549216340697; Sun, 03 Feb 2019 09:52:20 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 3 Feb 2019 18:52:09 +0100 Message-ID: To: "Christoph M. Becker" Cc: PHP internals , colder@php.net Content-Type: multipart/alternative; boundary="000000000000aaec05058101099a" Subject: Re: RFC Weakrefs From: krakjoe@gmail.com (Joe Watkins) --000000000000aaec05058101099a Content-Type: text/plain; charset="UTF-8" Afternoon Christoph, I can't really think of another name ... it's ... a weakref ... Probably using the PHP namespace makes most sense. Cheers Joe On Sun, 3 Feb 2019 at 18:40, Christoph M. Becker wrote: > On 02.02.2019 at 09:35, Joe Watkins wrote: > > > Some time ago I brought this up for discussion, and last night was > reminded > > of it's existence, and so this morning rebased and reworked the patch a > > little based on the feedback I got back then. > > > > Since it was long ago, and there's no particular rush, I don't intend to > > open voting until the current policy adjustment RFC's are resolved, but > > wanted to give everyone a heads up and ask for any feedback you may have > at > > this time. > > > > https://wiki.php.net/rfc/weakrefs > > Overall I like this. Thanks! > > However, calling this class WeakRef would introduce a potential BC > break, and would be a particular issue regarding the PHP manual, which > does not allow to document two classes with exactly the same name. > > Even if Etienne would officially cease the further development of > PECL/Weakref[1], having a class with the same name appears to be > confusing at best. > > Maybe another name should be chosen for the class? Or maybe we should > finally introduce the \PHP namespace? > > [1] > > -- > Christoph M. Becker > --000000000000aaec05058101099a--