Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:108088 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 80887 invoked from network); 10 Jan 2020 15:36:26 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Jan 2020 15:36:26 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 23DF21804F2 for ; Fri, 10 Jan 2020 05:42:20 -0800 (PST) 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, RCVD_IN_DNSWL_NONE,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-lj1-f178.google.com (mail-lj1-f178.google.com [209.85.208.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 ; Fri, 10 Jan 2020 05:42:16 -0800 (PST) Received: by mail-lj1-f178.google.com with SMTP id u71so2156355lje.11 for ; Fri, 10 Jan 2020 05:42:16 -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=OrKwdMFEJ1lbDZZoc8DWtnIKHrgmLFDgYqyRau9+JqU=; b=td9pUAfKtqyNZDltiKxGHTc19Aj7GRXGw7/elyWzAjmPK61DMojsmvRNgUQePEENSk TlsQWEBkWnxCoyKufhS0tvbJ8ggYuAiWZu66EofvVHSLzmX4bFpicUEsR5yFEX79T0DM odFFnRfzpd3suL71c1U7Gfw1KBgz0dnYl32e/O7Rjqv8xEgxVu5qQGGTVPlza/ArHBRu vx80/aGhjIABxIfKsHTDbNIuEErga06lTJEUDn3LLHC67nCdJFWR44lxONPlHICTiTak MqkQQjufkszkRxZvizXQikhWKAAdsy4/w/RCMVcdJL0772641jluC7KsfibWzHK1FXel SDWQ== 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=OrKwdMFEJ1lbDZZoc8DWtnIKHrgmLFDgYqyRau9+JqU=; b=Ap6bCMuW3KuDGyikABCEr5jIPBn4OAtrx0G1D0d2b0e8bgCZM2QBwZ4XmcNUrg1dA9 lSvNKLVWtQXN4yF9qcOtE2Z9SKOcC+LUpyKwzHFiWpPrqwjeP5Hj9UJo9/FqX8Sk8qjN 1toGG4i9AhWm1UcuMt2VUx3QGtEtOoXYW70J96s1b/2nNKXg1leIAZZMrNt+xUQG9KvS VynrxhhpzHJpDAwJff1dMjApuChoMe3Cu2QRHjQGCUUyzeagSi9NV3fmGFss+N2zZyzU l1/uUiEaJBI6nowCj1wSTZPP0qU7TVeVi/IRLOmPpuSLOzt8PePlwyP00igQy/hOHMqp VCEA== X-Gm-Message-State: APjAAAVyXxM0vGpUZwgbVESxvU4b2pPo9/jAquOiPym9+OaZhzv4hC5K K4esSBeNn3ZaHzCkwEjUeGIijdnvEPRhBPNonw== X-Google-Smtp-Source: APXvYqwUCxI9Z2tHxeN03MHnJXYefO0oWTBdPkGGK2ifsQ2s9iNi0UOBAEBEdRpU42sWZgK4bCrj/rY2Nt96QUvnxzY= X-Received: by 2002:a2e:884d:: with SMTP id z13mr2825075ljj.116.1578663732036; Fri, 10 Jan 2020 05:42:12 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Fri, 10 Jan 2020 14:42:00 +0100 Message-ID: To: Nikita Popov Cc: Rowan Tommins , PHP internals Content-Type: text/plain; charset="UTF-8" Subject: Re: [PHP-DEV] What to do with "$array[foobar]"? From: guilliam.xavier@gmail.com (Guilliam Xavier) Hi, On Thu, Jan 9, 2020 at 1:05 PM Nikita Popov wrote: > > [...] we already support > "$string" and "$object->prop", so it is in a way natural that > "$array['key']" is also supported, as the last of the "fundamental" > variable syntaxes. What about rather deprecating "$object->prop" too? The current situation can be surprising: "$object->foo()" // $object->foo . '()' "$object->obj->bar" // $object->obj . '->bar' "$object->arr[qux]" // $object->arr . '[qux]' "$array[arr][bar]" // $array['arr'] . '[bar]' "$array[obj]->qux" // $array['obj'] . '->qux' In any case, I'm +1 for deprecating "$array[key]", and "$array[0]" to avoid introducing another inconsistency. -- Guilliam Xavier