Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109443 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 22418 invoked from network); 30 Mar 2020 04:15:20 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 30 Mar 2020 04:15:20 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id C18291804C2 for ; Sun, 29 Mar 2020 19:41:09 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-vk1-f178.google.com (mail-vk1-f178.google.com [209.85.221.178]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 29 Mar 2020 19:41:09 -0700 (PDT) Received: by mail-vk1-f178.google.com with SMTP id f63so4291190vkh.0 for ; Sun, 29 Mar 2020 19:41:09 -0700 (PDT) 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=BBDDqiYC1DmwsWWswAXi54EuFTxKafi9BlOiCbRVkWA=; b=DuRQI463KZxqZdD9IWClDh7PLFQP8sVNj0Tr6Cf7v3UIbHFkFSudVWQAmKaZ+nRmFi 9PCbtqe1rGpi0DPzWRf9Y1ooX6GALvH8U04k2xrIYWVTpPPyEyyNWeHe3unhq3fQYq8B n+zz61dzwkOuHt3Apf6It91RQQl6pyeL8ZFOP28A9Q8n4102r2BcgOJp0P5RdxjdtJnC dsG9rMXKBS5pUlepBXnB+YUgmyS1vL7cXmwgE0I6PH2WifKej+6DDq25UzXvadqU+wI3 joIrzSvaCDC5WIhN7rK9fhIN2IiJvQkmuW5BHYH23nTxQJn2VM9QlqbgkzNBKVi4OmaR NxMg== 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=BBDDqiYC1DmwsWWswAXi54EuFTxKafi9BlOiCbRVkWA=; b=ibSssvvw4hKdCBqjXoyYp/fLVDaILGqgk0F+Fwn7mE00e+aG3NPMhPG7mPH9n8k7i+ SRjd/1m3SuNxNY4LowBbORiTsdopw8D82fvcj4kJeaXfzOSYLv6DNeSr+2BlDSy40EZK ZIUppUVgzFZ7zYSGgESGNUSB1FsfWlufkmWVt0BFJX1sgrZX2nNSsTaJqbYnG25+jEJM OdcCikDKk2iscmDhqz4r9Sor8dDFC4JvKIhmTbX2tUWBy3PacOxMUSZm+5Xp6aO7nsrf MXnT+TDQXu4m5WjGk+7Wwg6RvBxkyG5f8mKpzAmfYQknkPD4LM8Uc0azRrpz2rB1983P YWpQ== X-Gm-Message-State: AGi0PuYmJ0E0n/W8CKAYtFFLzM5mMnvCVIOmyeYZB89kxLpUfiiU3KnM 8eje/0TBTXvMALeTL6GYyjgCyYa2IfbJIgfbWWo= X-Google-Smtp-Source: APiQypLNDXbWj2ozaxeo7SiNbgq1csJ0Yu7JNV+tPKEand0TG4OtnUSUK3T4KdKk6+4lBu30/ou+uNJ2n0C00warsUI= X-Received: by 2002:a1f:2c4b:: with SMTP id s72mr6365549vks.93.1585536065444; Sun, 29 Mar 2020 19:41:05 -0700 (PDT) MIME-Version: 1.0 References: <5e81245c.1c69fb81.f7bcc.dd65SMTPIN_ADDED_MISSING@mx.google.com> In-Reply-To: <5e81245c.1c69fb81.f7bcc.dd65SMTPIN_ADDED_MISSING@mx.google.com> Date: Sun, 29 Mar 2020 22:40:54 -0400 Message-ID: To: Andrea Faulds Cc: PHP Internals Content-Type: multipart/alternative; boundary="000000000000f5a0d305a20961e5" Subject: Re: [PHP-DEV] Re: [RFC][DISCUSSION] Change var_export() array syntax to use shorthand arrays From: theanomaly.is@gmail.com (Sherif Ramadan) --000000000000f5a0d305a20961e5 Content-Type: text/plain; charset="UTF-8" Hey Andrea, Thanks for that. Good catch on the stdClass and __set_state parts. I neglected those in RFC, but I will add them. But they are still all forwards compatible changes so no major impact. On Sun, Mar 29, 2020 at 6:42 PM Andrea Faulds wrote: > Hi again, > > Andrea Faulds wrote: > > Hi Sherif, > > > > Sherif Ramadan wrote: > >> I'm proposing a new RFC to change var_export()'s array syntax to use the > >> short hand array syntax instead. > >> > >> The RFC is available here > >> https://wiki.php.net/rfc/var-export-array-syntax > >> > >> This is a forwards-compatible change proposed for and targeting PHP 8.0. > >> > >> I'd like to open up discussion. > >> > > > > What about stdClass? That is currently exported using an object cast > > applied to an array literal, and that array literal uses long array > > syntax for consistency. I think this should be mentioned in the RFC, > > whatever choice you make. > > Oops, I forgot about classes with ::__set_state! (I only thought about > stdClass because it was me that added support for it, unlike for > __set_state.) That also uses the old array syntax. > > Thanks and sorry for spam, > Andrea > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --000000000000f5a0d305a20961e5--