Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110870 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 25639 invoked from network); 7 Jul 2020 23:41:10 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 7 Jul 2020 23:41:10 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8DE381804E2 for ; Tue, 7 Jul 2020 15:31:55 -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-oi1-f170.google.com (mail-oi1-f170.google.com [209.85.167.170]) (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 ; Tue, 7 Jul 2020 15:31:55 -0700 (PDT) Received: by mail-oi1-f170.google.com with SMTP id k4so36190711oik.2 for ; Tue, 07 Jul 2020 15:31:55 -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=IEanMascvVZxzInxac3EDzppjKknFZc6dN3OF+FJdlU=; b=VCtvVUbyJYNHgUahTBWSTvG3WrFu3gkLvcptfKWtuRg/hBjR4vTKeDuv1QLdiSINEg RzbVHZ+77QNmt1GVgp8s80X7O7wvmV6LBxYHW0jPHP/WGLf/bUnVpSn0zdc+CpISDYmE HcWKGF8/j4PjJQP7Y89mPTIjKZ4Rbo09rcAeXWLbVWU2SgXXSEcl41Kyr2jiPVFpFuE0 DmTwDkB7WjWcxkrk3ILbWMGsaaF9sjxkOL9p6ADrm8bUOU+qbqZ84GCaCe5UBxDhD3HJ TQyXPbE6KR0+9+PmjPrr8Izjctr6bKQ/Qga9B4RdshzmjMQnVjQcry018rQ+vS41n5NV xsCw== 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=IEanMascvVZxzInxac3EDzppjKknFZc6dN3OF+FJdlU=; b=Rc0RZll8EvrHkekdQxb8YmN071ptx7IFAWjYxzbDjPvqJR5KohSJwIod1yWr4d4eoz DJj8m6+q1VdcqzkTPRYKUAZhH4fuCyOzKw6+DyV/ouYIM8u9tapNUZCzRzkvEgqiTQLH bM69LGZ4KmRprQs+MRS03QrPX13WBdQnNp7+oNI0SZmfz9bZrno/j19WhX8nyRXWx/dL qS3DDd2QHw2Q3vQvojJV3gxT7mrQZiUQpa0wmPxDlGuOwVFTzjjDxGv6LINq00mRjQs9 OdRPsKymy3O1TFDrJIk8jOICy2/6WpBmqptZbcXE/ROrie13sw5eegPoko217kgJjOyy h0Sw== X-Gm-Message-State: AOAM533QJ2DOCSv56+G2HGEdLlriaf4JPETCNwWUGV5mhsUtAIyfdKAd N6rzlq7w3I7olOwFuwmpumiVNJReGR20PhKCsMU= X-Google-Smtp-Source: ABdhPJyZawNNA2KEcCGGlIsWRNcFiyQzRTOOlri6PewliLBHLB65M/za8qolpDYsAPgmEyG6XjjJ8vFFZn3z7Yw97T8= X-Received: by 2002:a05:6808:aa2:: with SMTP id r2mr4911959oij.162.1594161114593; Tue, 07 Jul 2020 15:31:54 -0700 (PDT) MIME-Version: 1.0 References: <0771c3ac-53ec-4a7f-a4e9-6ae3c9b1f1f6@www.fastmail.com> <49fd7972-8cec-4207-99af-6c77c2328211@www.fastmail.com> <70889678-d469-0f94-3c5e-e86fcd03b22b@gmail.com> In-Reply-To: Date: Tue, 7 Jul 2020 19:31:25 -0300 Message-ID: To: Larry Garfield Cc: Miguel Rosales , php internals Content-Type: multipart/alternative; boundary="000000000000f33d4705a9e18e24" Subject: Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics From: david.proweb@gmail.com (David Rodrigues) --000000000000f33d4705a9e18e24 Content-Type: text/plain; charset="UTF-8" There are some problem by using double back slash for PHP namespace? Eg. Instead of \PHP\String be just \\String. Em ter, 7 de jul de 2020 19:04, Larry Garfield escreveu: > On Tue, Jul 7, 2020, at 4:22 PM, Miguel Rosales wrote: > > Larry Garfield wrote on 07/07/2020 16:46: > > > This has reached the 2 week mark, but there's not been much > discussion. Anyone else want to weigh in? > > > > > > > I guess I'm missing something obvious here, but the RFC says: > > > > > 5. Component or sub-component namespaces MUST use CamelCase naming > > conventions. > > > > But then in the examples you've got e.g. \PHP\DOM\ or \PHP\SPL\... isn't > > that incorrect? > > > > And slightly related, is there any reason to use \PHP instead of \Php? > > > > Sorry if this has been discussed before, I haven't seen it. > > > > Cheers, > > Miguel > > Mm, mainly because I added the CamelCase clause late and didn't think > about abbreviations. Whether it should be PHP/XML/DOM or Php/Xml/Dom has > been an ongoing debate for at least since PHP 5.0. I have no preference > strong enough to die on that hill, though, so whatever voters are willing > to go for I'm good with. > > Anyone care enough to offer a bikeshed color? > > --Larry Garfield > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php > > --000000000000f33d4705a9e18e24--