Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:111249 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 20201 invoked from network); 29 Jul 2020 17:53:38 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 29 Jul 2020 17:53:38 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 6EDE91804DB for ; Wed, 29 Jul 2020 09:49:46 -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=-0.2 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-ot1-f51.google.com (mail-ot1-f51.google.com [209.85.210.51]) (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 ; Wed, 29 Jul 2020 09:49:45 -0700 (PDT) Received: by mail-ot1-f51.google.com with SMTP id l27so10834374oti.3 for ; Wed, 29 Jul 2020 09:49:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=cUacC8yJmdm3TR0/IzFKwYL3RGV2Cn1jo9syXrrqDdg=; b=gqXa5PK65ivuwfahTdufiKbBg8+3O277x3iAYqayDrHWYppEUArfV7kMGOlscOMgyp puEIFAnwPkgN9s0HZloYDU91fJtaeLBg1hmbaa2ZreEoS3L7+DSUwHMRYvDLInsdZQr4 sbDKKO+bLmS3MToI86Vqo1Bc8KFdDnrCZz5dueXhaxMmFajkbVzjvzpH37u72t8EDdTU TvrDmoTtm2xRdyZ9sEz9Iu7ciORmhDW1EMdbCvVmZmVLyPR2VTtumYL15zB0/tO8z+vt A3fhMcQHpWjWxuR5hxOL2dXhKNHFA2XFdBcsqb6RkSmxE91S+ZcVWOJa/iReNLRczcxJ /Csw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=cUacC8yJmdm3TR0/IzFKwYL3RGV2Cn1jo9syXrrqDdg=; b=kMwi59/nwmpzxoE0l5F8yO11/2S7G9dxgjod/mRK8T5Mdu9fHJgBDzuMlfBAiTwZ0t CPnJzGRhC2mPkss/L58P7ruWWpZ+TtX4P35/pxJaCKR/FlqVf6HVi/LSh8deTSEVm45W LwZ9fVpdI17KxpqRJQ6O9F+QrNP+eveYNpkRWxMaVD7Hy+cJwn1xs9zL7QbtyOBt3Wmy PIapvy2kfw3u1wUWbICVY2sk9SKO4qrXmEl0VnYvOEncAj6NLdtbosSJmOJWqmC9eJ1F 6vaeSzhEshUO4zm427LA6cC/kU8/eW4cU5NMAMHPoQnpy8m8iR0Jo3K67G0dIodcV+21 E4Lg== X-Gm-Message-State: AOAM531tUVnaHK7T1379U99SzMEJAiNKUO4Y2bPCaH17YKI5F8BDraRF hQMU7J6bIyFsoX/F98iqOyy1N4/0PAyme1DO+LUEtQ== X-Google-Smtp-Source: ABdhPJxcF45H1nV4jLthtCqLEEiCqp9cqKrvS/AWyjh0KoC4JIA0/AqxOBMtW2bpFbuBFXAddFWUB3mbAXk1jcW4AOY= X-Received: by 2002:a9d:5186:: with SMTP id y6mr15806332otg.230.1596041382200; Wed, 29 Jul 2020 09:49:42 -0700 (PDT) MIME-Version: 1.0 Date: Wed, 29 Jul 2020 13:49:28 -0300 Message-ID: To: PHP Internals Content-Type: multipart/alternative; boundary="000000000000a20b1705ab975785" Subject: Allow two words keywords From: david.proweb@gmail.com (David Rodrigues) --000000000000a20b1705ab975785 Content-Type: text/plain; charset="UTF-8" Hello! I do not know if there is some consensus about "why not use two words as a single keyword" in programming language in general, but I really found a few examples of it, as in SQL with "GROUP BY", for instance. So I question if it could be used on PHP to expand the keywords repertoire by mixing two words without causes BC. I will use the Attribute syntax-war to exemplify. I really prefer to create a new keyword "attr()" or "attribute()" to make attributes possible. It basically uses the same function-like with arguments to work. But it invariably will cause BC to old codes that use attr or attribute names (eg. "function attr()"). But, if we create a new two-words keyword like "using attr()", maybe it will not cause any BC, because "function using attr()" is impossible, but "using attr(X) function attr()" will do. I do not know if I am being high with peanuts, but maybe it could be considered to this discussion and make possible new features on PHP without creating strange symbols like @@ or #[] that will requires that new users check the documentation about "what it mean", while is very hard to Google symbols (so search will be "what mean double at in PHP" or "what mean hashtag brackets"). Atenciosamente, David Rodrigues --000000000000a20b1705ab975785--