Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:95355 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21191 invoked from network); 21 Aug 2016 20:20:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Aug 2016 20:20:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.46 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.220.46 mail-pa0-f46.google.com Received: from [209.85.220.46] ([209.85.220.46:36273] helo=mail-pa0-f46.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C9/E7-50790-11D0AB75 for ; Sun, 21 Aug 2016 16:20:33 -0400 Received: by mail-pa0-f46.google.com with SMTP id pp5so30728124pac.3 for ; Sun, 21 Aug 2016 13:20:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=oDrt072gn/A+LD3T2bLu2X1/0YO/mMaYZDKPERXYxw0=; b=F3QFK8Bwom+xBWzocn2haXjxmHfCjOzHf//GAmT42KYDM83PCoSV71TJZn6PEPagJM 6kJoi1DwV4FZlqjndmcMFwbUSCI5KyqKjI3FunpmmQr2etAximFKIGGkqMUlMaqIiL65 q8OdlrtnZmkG3Sy7hVfhhL8TZEmQR/nZyXxOSgKjJRLUEB+HZ+pScQGw315kTrorBCVk bYd/MKdfm7bJrhiG2ARghpVtJC43PeCItTBvM2rkKE65VYGNYcUrPDuf2WrMdvEBTtfN kDCYTj8VwaBBDi/R6NjUlDqXMtBD3h3bJlEOlcw+Th7zrqYOep7RoNAFf+c7gIVAIwpY zU4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=oDrt072gn/A+LD3T2bLu2X1/0YO/mMaYZDKPERXYxw0=; b=JpGOLZQrt3B5i+VaTo1IOHkoEVmU/5wmFF2iY8NaHUoeGB+a/m+CELwumL8TIb3ek6 oeEFodTNk1SBmjoY2TZKMYd7hoArepHUaVb0GgqiHhrKjGz7FI1osSg4JsrFPganaqTb HTwDpQdYX+JRh87xgDa9UV6IGjWG18+XaRdGMHxt6+0oNFUvs1xmIPg+qkS/E8QB2SG4 TIKU4uuzQaqF94MyFirZnuxOWtz7NUTX1nZypI9NGfUwmg3qTlDKkePwcI+iMej4urGT PrN6RXBqYkxP8ETumC/zBy+VwYLUNI1Jt0+Ks2zKAZCCBB8KxKTFmTHOr8Qr/v5oZWUN hUIg== X-Gm-Message-State: AEkoous4Gm3cJhPe+Yt1C9j0biZUTI++wtWSN2lp9wRwFrl350FQM32FcbExxfiJPKgqQdk11pKVe8A8c3Cgvg== X-Received: by 10.66.54.132 with SMTP id j4mr35724161pap.110.1471810831001; Sun, 21 Aug 2016 13:20:31 -0700 (PDT) MIME-Version: 1.0 Sender: morrison.levi@gmail.com Received: by 10.66.24.42 with HTTP; Sun, 21 Aug 2016 13:20:29 -0700 (PDT) In-Reply-To: References: <0668D584-EE51-4932-85D7-01D8BF70E409@trowski.com> <15E198DD-FF66-475D-ABBC-54ECD2B6BF62@trowski.com> Date: Sun, 21 Aug 2016 14:20:29 -0600 X-Google-Sender-Auth: 3PxE8tsR8kJ7m5JQgwblId8PFTk Message-ID: To: Marco Pivetta Cc: Dan Ackroyd , Aaron Piotrowski , internals , Stanislav Malyshev Content-Type: multipart/alternative; boundary=001a11367696c22e36053a9aa923 Subject: Re: [PHP-DEV] ReflectionType::__toString() prepending \ to class names From: levim@php.net (Levi Morrison) --001a11367696c22e36053a9aa923 Content-Type: text/plain; charset=UTF-8 On Sun, Aug 21, 2016 at 1:52 PM, Marco Pivetta wrote: > I still want to see code that outweights these commonly used open-source > tools before you grab that argument again. > > As also said by Dan: new features => adaptation required. > > Supporting `?` in your own home-grown internal code-generator is something > you can do as part of a 7.1 migration path, exactly like we'll have to do > with the OSS libs. > > That said, I'm muting the thread: I'm basically wasting time with this, > apparently. > > > Marco Pivetta > > http://twitter.com/Ocramius > > http://ocramius.github.com/ > > On Sun, Aug 21, 2016 at 9:48 PM, Levi Morrison wrote: > >> The issue here is around changes that affect old features (__toString), >>> where the behavior changes depending on whether a parameter is defaulted or >>> not (also a previously existing feature) >>> >> >> Which has existed for only one release. This is a small BC break and is >> intended. We previously had nullable types just no way to really encode it >> as a type. We now do. Breaking code for one single minor version is >> perfectly acceptable, especially given that there are other codebases that >> will break if we do not include the question mark. >> >> > There is a BC break either way. I do not understand why you cannot seem to fully understand this. If there is a BC break either way why not stick with intended behavior even if it breaks code for a few tools for a single version of PHP? --001a11367696c22e36053a9aa923--