Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114689 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 35326 invoked from network); 2 Jun 2021 07:44:25 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 2 Jun 2021 07:44:25 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id B42501804D8 for ; Wed, 2 Jun 2021 00:57:37 -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,NICE_REPLY_A, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (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, 2 Jun 2021 00:57:37 -0700 (PDT) Received: by mail-wr1-f46.google.com with SMTP id h8so1259518wrz.8 for ; Wed, 02 Jun 2021 00:57:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=bqs+eVGOjK6irWw5tIl1CaZK49M9ivvf4GgSDMFFSKU=; b=d9avZeQQooEc6Go7QAro1BvGDo93QqF3v4F1gIh3z8aLDqpKpIZrGPUJUeis/YG+Cq Skp2QaT/TR6X4VfT89Dcp4jmvZ6bxw2dUzey034d6g3Hh/mias8sHp93a1oJyUWg1Qby 4AvAgqUus3SIjHPbwxlLil4XFztgUR43M6nBnMz7ZyCsf+odK4Ja+ZWDRUI13AFAEPEO MIKK8/miROLd18MoD4s6gweRgY4gb4Nk4aNF3A6b0Cr6eUnusmq6Gb2tCsl8HHDx1kvg Faibjfc6XtyB0Zh00X5eljCkOQUxtFBfx7Dtytc05wlOIPpIsAtwDZSH2yeaYuTH1sN+ fs3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=bqs+eVGOjK6irWw5tIl1CaZK49M9ivvf4GgSDMFFSKU=; b=kUm3Sq/4/4j8Wrqr6TrrTv6E3Ccv30+IISA9nn6wbNDBahVZwcio4Lh2B5Nni/yiZ7 GIYYrlGiWWvHA5FahTQuWOMtRo0dm1go+JDVHI40svUaCu0SkAEH7gxkY19VDPpHwle9 N6d9qvGvcGrKwZEi/HjG7piexF16jnBUbXRNW925zLcZrSQBkDCggL+ItiY6dVz3GIvh L69X6uL8f9e46dSnAvwbe4Z0zXICHU3LmmzKvaboPranGXgvAl7V7ROvOJRuv/3S+kJ3 U4dmjo2kdVzp7x0FTwdsEZpyQVMhr3pW4bl5fqiYUPBZk6IKSBRRQCubTRQGqz5SU0xe wgeA== X-Gm-Message-State: AOAM5309351N+ygSoWVvwjJVs8uE+Um3QCWgpZfR+LVt6cBiD06QmQZ/ /ZBY1nlvIWBKs+NRroGw34yIjXAAnQs= X-Google-Smtp-Source: ABdhPJzMoqKj2rJHG4u0+qAb2kxYK5H4d3PinMOYWhV2kpDYgLaIuTwG4lHoIFjzIeDepTlnKZ3b1w== X-Received: by 2002:a5d:4d05:: with SMTP id z5mr31498613wrt.127.1622620653517; Wed, 02 Jun 2021 00:57:33 -0700 (PDT) Received: from [192.168.0.22] (cpc104104-brig22-2-0-cust548.3-3.cable.virginm.net. [82.10.58.37]) by smtp.googlemail.com with ESMTPSA id f5sm6195532wrf.22.2021.06.02.00.57.32 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 02 Jun 2021 00:57:32 -0700 (PDT) To: internals@lists.php.net References: Message-ID: <746dce55-ef2e-c5d5-9318-b5fb2e899b90@gmail.com> Date: Wed, 2 Jun 2021 08:57:32 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Subject: Re: [PHP-DEV] "Namespaces in bundled extensions" and iterable additions to the standard library From: rowan.collins@gmail.com (Rowan Tommins) On 02/06/2021 02:30, tyson andre wrote: > - Did anyone have feedback on whether iterable\ or Iterable\ makes more sense - Personally, iterable\ seems like it should be an exception due to it also being used as a soft reserved keyword that is typically lowercase. To me, a lower-case namespace like "iterable" just looks wrong, because I'm so used to namespaces, like classes, being UpperCamels. The connection to a keyword doesn't seem convincing to me - if anything, it highlights the possible confusion from choosing a namespace name that has a different meaning elsewhere, although I admit no brilliant alternatives spring to mind. Regards, -- Rowan Tommins [IMSoP]