Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101175
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <12F58DFE-B842-44FB-ACF6-FB62F4BB1F7A@gmail.com>
References: <CALOUi=AE8dP=bN=EaQUASXeDgcMpPEL+T-5rzNn5zKUiQEDmtw@mail.gmail.com>
 <12F58DFE-B842-44FB-ACF6-FB62F4BB1F7A@gmail.com>
Date: Mon, 27 Nov 2017 22:38:15 -0500
Message-ID: <CAEUnE0dz5CYThppuxtPyUZhSNjeBFzcUD8Q4V0kNyHhce_hxiw@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c0bb534d0d0c3055f02bf57"
Subject: Re: [PHP-DEV] Changes in namespace importing
From: tendoaki@gmail.com (Michael Morris)

--94eb2c0bb534d0d0c3055f02bf57
Content-Type: text/plain; charset="UTF-8"

I'm sure the internal coders will correct me if I'm wrong on this, but as I
understand it PHP has no notion of packages, yet many calls to modify how
namespace importing works seem to be under the illusion that packages
exist. This is understandable, packages are namespaces are terms used
somewhat interchangeably. However, they aren't the same.  In Java,
Actionscript 3, and I presume C++ and C# when you import a package you are
binding it to the resultant executable the compiler will create. This will
affect the size of that executable regardless of how much of the package
gets used, or even if it gets used.

PHP has packages, but they are compiled in when the interpreter is compiled
and set up on the machine. Adding a package in PHP requires redoing that
compile step and modifying the php.ini to enable the associated .so file.
As for libraries looked up by composer - these are never referenced until
they are called for at runtime and the autoloader gets invoked.

As a result of this PHP's "namespace" resolution is nothing more than a set
of string replace rules done at call time to try to resolve the name to a
known class. It's a convenience shorthand for programmers, but a powerful
one. Also, it has it's limitations.

On Fri, Nov 24, 2017 at 8:21 AM, Rowan Collins <rowan.collins@gmail.com>
wrote:

> On 24 November 2017 07:05:52 GMT+00:00, "Khawer ." <khaweronline@gmail.com>
> wrote:
> >We use 'use' keyword to import other namespaces, namespace classes,
> >namespace functions, and namespace constants.
> >
> >Example
> >1) use abc; (Import abc namespace)
> >2) use abc\ClassB; (Import ClassB  from abc namespace)
>
> Although these are described in the manual as separate types of import,
> they are actually the same: they alias a prefix used to rewrite class names
> when you mention them.
>
> If you have a class "One\Two\Test" and a class "One\Two", then "use
> One\Two" will allow you to access them as "Two\Test" and "Two",
> respectively. https://3v4l.org/nQ7pB
>
> Similarly, if you alias a prefix with "use Foo as Bar", then "new
> Bar\Test" will refer to class "Foo\Test", and "new Bar" will refer to class
> "Foo". https://3v4l.org/2r6WN
>
> So "use class" wouldn't make sense, because that's not actually what
> happens.
>
> Regards,
>
> --
> Rowan Collins
> [IMSoP]
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--94eb2c0bb534d0d0c3055f02bf57--