Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99302 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55143 invoked from network); 31 May 2017 16:52:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 31 May 2017 16:52:43 -0000 Authentication-Results: pb1.pair.com smtp.mail=dave@mudsite.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=dave@mudsite.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain mudsite.com designates 209.85.218.54 as permitted sender) X-PHP-List-Original-Sender: dave@mudsite.com X-Host-Fingerprint: 209.85.218.54 mail-oi0-f54.google.com Received: from [209.85.218.54] ([209.85.218.54:35068] helo=mail-oi0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 33/1F-43873-7D4FE295 for ; Wed, 31 May 2017 12:52:42 -0400 Received: by mail-oi0-f54.google.com with SMTP id l18so22934967oig.2 for ; Wed, 31 May 2017 09:52:39 -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 :cc; bh=rIUtwwzqGTSx+8/2B01smFhK/IeRzzW+yoSleFQX590=; b=n0/E6YCs67+33EhJhafRbVnBo/HEn9BANDl/8LxguuXn1GJFhkuOxtfB8Rv1JyMHAS qtL4MRBkBgo2DmZZ516rQbOgUYY78hNt8b/b4srdAZRn6ULzJekrDBe3Nrj0kRElUO16 ydX7k/WZ7Gm564ZQkW/Il8W7OdyXJAHl8o0Bej9g+0KeL4jH3Sp3UiLrWd8/265m7tu2 /KRBnR+NAep/y1QlfBcjhhEoppGHQu0+a9TjlzpkQzeSP+IcAHbArUboVsyQBYPqoBBK SzGZ1fNZKMSzqAoE8XPBgf09k/jmTGp9ZMNliLNyZZBpOrMfHiWgHAGm/4J6qeHc30EK ojdw== 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=rIUtwwzqGTSx+8/2B01smFhK/IeRzzW+yoSleFQX590=; b=nKBu9zf7p9ecQN4z96A2E6yIacC4R0la0Yii3d49FM04C/v0CIFtFOtYZzfqvRRFtY y/fdZoOWe/5yo5OkSlO2s3XgE/DVJeDyuVP27F37xsRuQEfnJ4rSAwJzeISoZBppCSsg Rr69/G92IX8EftvTZieG8m265kwpUyKpp6A22le1SIixVsXE9TT+IuWE7SPLL8qTJYeh jh+AdNQybsDfQlv/2CdJETNAwbDWHRjU1sjPl7hi7XHnhBE6aKtsSavxhsbAR5tie8Xd fEMn9O1fkSiSKF0D63ZQgl2Y5CaBL1Dey0ND76JViLj/H3rscE6KUgSuFm4iagzyuA4I gHng== X-Gm-Message-State: AODbwcCKUA9zjvPuuj9xr3fSy8HsT2Jfts1Aw7c3/CtT1LT5zYezfTcf vp0QxkHqDzIFJjJSZqY+jH4+SE7sdkP1 X-Received: by 10.202.81.203 with SMTP id f194mr13158130oib.204.1496249556700; Wed, 31 May 2017 09:52:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 31 May 2017 16:52:25 +0000 Message-ID: To: Dan Ackroyd Cc: PHP internals Content-Type: multipart/alternative; boundary="001a113d789c52a18d0550d4bf60" Subject: Re: [PHP-DEV] [RFC][Post-Discussion]: E_WARNING when using array-index on non valid container From: dave@mudsite.com (David Walker) --001a113d789c52a18d0550d4bf60 Content-Type: text/plain; charset="UTF-8" On Wed, May 31, 2017 at 10:16 AM Dan Ackroyd wrote: > Hi David, > > On 11 January 2017 at 15:42, David Walker wrote: > > Joe had requested renewed discussion on the accepted RFC[1] and my > proposed > > PR[2] be brought forward again for implementation discussion, and to come > > up with a resolution. > > > > Any > > thoughts on a better implementation, or other use cases that need > attention > > would be appreciated. > > > > Please could you give us an update on the status of the > implementation, and are you still looking for advice on how what would > be needed to complete it? > I had sent out messages on the subject a while back and heard nothing in response. So I had assumed without more discussion it would have been merged at some point when prepping for 7.2. So if there's continued problems, and or issues, I'd be receptive to hearing about them. However my time to dedicate at it currently is pretty minimal, having recently taken a new job, most of my free cycles have been going to read/learn where i'm at now. cheers -- Dave --001a113d789c52a18d0550d4bf60--