When PHP resolves a function name with a namespace, it is preferred to look up the functions in the current namespace, and then determines the call target based on whether it is a relative path or a fully qualified path. The specific rules are as follows: 1. Unqualified function names (such as hello()) are only searched in the current namespace; 2. Relatively qualified names (such as Sub\hello()) are resolved based on the current namespace; 3. Fully qualified names (such as \hello()) are searched from the global namespace; 4. Functions are not within the automatic loading range and need to be introduced manually; 5. Function alias can be set through the use keyword to simplify calls; 6. Global functions may be overwritten by the namespace function of the same name, and the global function needs to be called explicitly using a backslash. Understanding these rules helps avoid call errors.

When PHP resolves function names with namespaces, it follows a set of rules that determine which function gets called based on the current namespace and how the function name is referenced. The key idea is that namespace resolution depends heavily on whether the function call uses a fully qualified name, a relative name, or an unqualified name.

Unqualified function calls look in the current namespace

If you call a function without any namespace separator (like \ ), PHP assumes you're referring to a function in the current namespace.

For example:

 namespace MyProject;

function hello() {
    echo "Hello from MyProject";
}

hello(); // Outputs: Hello from MyProject

Here, hello() is unqualified, so PHP looks for it inside MyProject . It does not check the global space unless told otherwise.

Qualified names resolve based on the current namespace unless prefixed with a backslash

A qualified name includes part of a namespace but not the full path — like Sub\hello() .

PHP resolves this relative to the current namespace:

 namespace MyProject;

function hello() {
    echo "Top-level hello";
}

namespace MyProject\Sub;

function hello() {
    echo "Sub hello";
}

MyProject\Sub\hello(); // Sub hello

But if you try calling just hello() in the MyProject\Sub namespace, it will look in MyProject\Sub first. If it doesn't find it there, it won't automatically go up to MyProject .

Fully qualified names start with a backslash and use the global namespace

To bypass the current namespace and refer directly to a global or specific namespaced function, you must use a fully qualified name — one that starts with a backslash ( \ ):

 namespace MyProject;

function hello() {
    echo "From MyProject";
}

\hello(); // Calls global function 'hello', if exists

If there's no global hello() , this will throw an error. So be careful when using fully qualified names — make sure the function actually exists at that path.

Things to watch out for

• Autoloading only applies to classes , not functions. So if your function is in another file, you need to manually include it.
• Function aliasing can help manage complex references:

   use function MyProject\Helpers\format as formatData;

  This lets you call formatData() instead of typing the full path every time.

• Global functions can be shadowed by namespaced ones unless explicitly referenced with \ .

---

So, PHP resolves function names with namespaces by checking:

• Current namespace (unqualified)
• Relative paths (qualified)
• Global or exact namespace (fully qualified)

It's straightforward once you understand the context, but easy to trip over if you're not paying attention to how the name is written.

Basically that's it.

The above is the detailed content of How does PHP resolve function names with namespaces?. For more information, please follow other related articles on the PHP Chinese website!