Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109666 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 56047 invoked from network); 15 Apr 2020 21:09:19 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 15 Apr 2020 21:09:19 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0CBB91804D0 for ; Wed, 15 Apr 2020 12:39:20 -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-ed1-f52.google.com (mail-ed1-f52.google.com [209.85.208.52]) (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, 15 Apr 2020 12:39:19 -0700 (PDT) Received: by mail-ed1-f52.google.com with SMTP id f12so2832016edn.12 for ; Wed, 15 Apr 2020 12:39:19 -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=Cr5Xef0gizPUTMvsU9SgdaENneJj8J7ZQZ7Wy2k+mCs=; b=dNvl3UdlA0uwmnW518VDgOrrZdOHPouk3lTRZf0pIwXgyF0QpW2dNggJgYVvbfni7H 1ZdqymQFtkB4IKjeRMpO0KbpRzFoqN3YgpR6uXUm3KqazRJNlVRQfNvtghSU6+wCcq01 fl8nVwvZLLZf25f67xWPy5T47zoPjbqBe24t2YX7eWmv1sUInKcY6QjLE4w98P3BNEt+ t/K/FwUG6sKe7prLflRLtP+TqSzZfulxvdvEme7QhJRprcEBUV2xoZ19aFZq77DYmkFl 6PA8hxLyMHZXJN5pMxmrpaBnfmeKcTau8nuh+kkgwRrdCRMxVv++xkq/X/ReslDR2Djz XvHA== 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=Cr5Xef0gizPUTMvsU9SgdaENneJj8J7ZQZ7Wy2k+mCs=; b=F0gWJsWOkOEdC1esFpvEiC6FR9Ts9bYG5haTeyEHwsrHu3h/mXzn0zWNCI7pu2rW3l SjVCHDvw5lofCEokabY53i4Uz+SaoAXkO21uDZ/czNFcZUpiH3sPSc5cIqTfHrSoH1v5 /+/WHIBdDUZ2y4RGLBSyu+tI7C+MyVOPr/INdAiN+/qbpd6VaJOh8MQUEDxOfImm7EKA Ol8rKklw+2Oaq48G9M6WXygACMYD8rDHXgDz0h8cHsFvw26xcjgu7hhRH3ujnW6fq8O6 Rgcu3tTFmop4HUEp/989iegArlEXoqwaRygHzcDZPk8C6CZvQTndaP7Rok3xDqZam/zc OFWg== X-Gm-Message-State: AGi0Pubr4INtyRMCFRm12yaXyMcxlB8xnefSi6r6afEzZ5SzpabqmSgy PQ8Q0E25LCzCjNqhMia8t+bbesoQ3Q44vzXdw17Kps3L3NI= X-Google-Smtp-Source: APiQypKiTkqx5CoFiozYNlECZexL0ShdE4alk2//ccRwAdc7io410OFIdYWNtll0dWvvllcKp9+UNDFtRTPzErhqXw0= X-Received: by 2002:a17:906:81d7:: with SMTP id e23mr6009260ejx.309.1586979557785; Wed, 15 Apr 2020 12:39:17 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: Date: Wed, 15 Apr 2020 21:39:06 +0200 Message-ID: To: Marcio Almada Cc: =?UTF-8?Q?Micha=C5=82_Brzuchalski?= , PHP Internals List Content-Type: multipart/alternative; boundary="000000000000cecf0605a35978b9" Subject: Re: [PHP-DEV] [RFC][DISCUSSION] PHP Namespace in core From: george.banyard@gmail.com ("G. P. B.") --000000000000cecf0605a35978b9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, 15 Apr 2020 at 18:39, Marcio Almada wrote: > > > > Hi internals, > > > > I hope you're doing well. > > > > I'd like to announce the PHP Namespace in core RFC for discussion. > > The RFC is authored by me together with George Peter Banyard and it's > > purpose > > is nothing more like to allow the use of PHP Namespace in the core. > > > > The RFC is described at https://wiki.php.net/rfc/php-namespace-in-core > > > > Best Regards, > > Micha=C5=82 Brzuchalski > > Hello, > > Even though I'm fond to the idea of languages having the official > stdlib contained > into a single space, there seems to be no practicality on a \PHP namespac= e > usage > at this point IMMO. > > We would be in a situation where things are either mixed in and out > the new namespace > - Should I `use function PHP\{json_encode, json_decode}` or was it in > the root??? - or > everything that already exists must first receive an alias into this > new namespace, to allow > consistency... but then there would probably be no plans ever to > actually move existing stuff > into the new prefix in the future. > > With the lack of a feasible roadmap, I'd rather vote on doing nothing for > now :/ > > Thanks, > M=C3=A1rcio > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > As mentioned by Michal, JSON is not a core engine extension, you can even compile a version of PHP without JSON support therefore compared to the parallel discussion this extension would not be included in the PHP namespace. Best regards George P. Banyard --000000000000cecf0605a35978b9--