Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:100078 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 62116 invoked from network); 28 Jul 2017 11:46:32 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 28 Jul 2017 11:46:32 -0000 Authentication-Results: pb1.pair.com header.from=narf@devilix.net; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=narf@devilix.net; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain devilix.net designates 209.85.218.48 as permitted sender) X-PHP-List-Original-Sender: narf@devilix.net X-Host-Fingerprint: 209.85.218.48 mail-oi0-f48.google.com Received: from [209.85.218.48] ([209.85.218.48:34225] helo=mail-oi0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3C/C3-40376-7142B795 for ; Fri, 28 Jul 2017 07:46:32 -0400 Received: by mail-oi0-f48.google.com with SMTP id x3so126626232oia.1 for ; Fri, 28 Jul 2017 04:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devilix.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RLTOSVizGq219r3HQXqKcD4mTJ3B3ezv/2B0830nUSA=; b=CMMFmHIoMUmAsyYPxWd/X51SB/tmb2KjXjU+a2IpmesSh++IvAMCuVTG1CHx8Sgse/ zObbE5WDiocVItK7tnGhvzNmB9olHbBNlnwF+XLwI1+u9hA4MehDmruWaeayp0AYXGwW 3zy+DahNRgqQPUMgaAkS93SqPrAJVq6CFClgA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RLTOSVizGq219r3HQXqKcD4mTJ3B3ezv/2B0830nUSA=; b=E91ZGS7a37udy8GzaDSHtOtY87wGayYhVYY60r2NYMfO7ELbXcjN8PggpFRDI++nNO gE9U28cBJGDl+3rF21hLdFG3A+gI6DSxZ1B12lUCSUnpNAh0sAvJBnoOm8/52NzUdfDu wDRZ82LaURmcz9yFW3oX49L5lfMTynnfQgtgfHop658GU3sgSHWcnWC0+dI38URoXGHR d+k9NEkfui9qaor67ZfbCmM7cnD2GeDFc5i6q/1pLgdv+ohfi2bfqjMbZHWGARmopm3Q w7WQb27tWbRdFWboS9bY3I/sJ65+clQs8kmcnzlAqVDYXW+H/nBspIAV80Mc7upx3C+q CPWw== X-Gm-Message-State: AIVw111uFCyVxnrthf9XPZ8FKN7R4B2aJbdr74+ZVpO18tbMLRVd29eU GWsOSPgsDFeEWgi/852U2b1C9c8PXl4E X-Received: by 10.202.188.196 with SMTP id m187mr5882277oif.91.1501242388269; Fri, 28 Jul 2017 04:46:28 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.115.69 with HTTP; Fri, 28 Jul 2017 04:46:27 -0700 (PDT) In-Reply-To: References: Date: Fri, 28 Jul 2017 14:46:27 +0300 Message-ID: To: Jakub Zelenka Cc: Craig Duncan , Nikita Popov , Internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] [RFC] Raise warnings for json_encode() and json_decode() issues From: narf@devilix.net (Andrey Andreev) Hi, On Fri, Jul 28, 2017 at 2:39 PM, Jakub Zelenka wrote: > On Fri, Jul 28, 2017 at 12:23 PM, Craig Duncan wrote: > >> Hi Nikita, >> >> Thanks for your input. Would you vote yes for throwing an exception? >> >> > Just to clarify exceptions are no go for 7.x. It would have to be 8.x and > it would be a huge BC break so I'm quite confident that this will fail the > vote! This is a long shot, but here's an idea: an OOP API throwing exceptions. Would require more work both to implement and use, but it would surely be less error-prone and there'd be no BC break. Cheers, Andrey.