Les espaces de noms
There is nothing wrong with PHP namespaces, except that those 2 instructions give a false impression of package management.
... while they just correspond to the "with()" instruction of Javascript.
By contrast, a package is a namespace for its members, but it offers more (like deployment facilities), and a compiler knows exactly what classes are in a package, and where to find them.
Définition de l'espace de noms
L'espace de noms est déclaré en utilisant le mot clé namespace, devant être au tout début du fichier. Par exemple :
Exemple #1 Définition de l'espace de noms
<?php
namespace MyProject::DB;
const CONNECT_OK = 1;
class Connection { /* ... */ }
function connect() { /* ... */ }
?>
L'espace de noms peut contenir des classes, des constantes et des fonctions, mais pas de code libre.
La définition de l'espace de noms a pour conséquence ce qui suit :
- Dans un espace de noms, tous les noms de classes, de fonctions, et de constantes, dans leurs définitions, sont automatiquement préfixés par le nom de l'espace de noms. Le nom de la classe est toujours le nom complet, i.e. dans l'exemple ci-dessus, la classe est appelée MyProject::DB::Connection.
- Les définitions de constantes créent les constantes, qui sont composées du nom de l'espace de noms et du nom de la constante. Comme les constantes de classe, les constantes de l'espace de noms ne peuvent contenir que des valeurs statiques.
-
Le nom de classe non-qualifié (i.e., nom ne contenant pas ::) est résolu au moment de l'exécution, en suivant cette procédure :
- La classe est recherchée dans l'espace de noms courant (i.e. en préfixant le nom avec le nom de l'espace de noms courant) sans tenter de la charger automatiquement.
- La classe est recherchée dans l'espace de noms globale, sans tenter de la charger automatiquement.
- Le chargement automatique pour le nom de l'espace de noms courant est tenté.
- Si la dernière tentative échoue, la recherche échoue.
-
Le nom de la fonction non-qualifié (i.e. nom ne contenant pas ::) est recherché au moment de l'exécution tout d'abord dans l'espace de noms courant, puis, dans l'espace global.
-
La constante non-qualifiée est recherché tout d'abord dans l'espace de noms courant, puis, dans les constantes globales.
add a note
User Contributed NotesDéfinition de l'espace de noms
Baptiste
14-May-2008 12:47
14-May-2008 12:47
SR
12-May-2008 04:53
12-May-2008 04:53
RS: Please go read a book on object oriented programming so you understand why namespaces are important, instead of actively discouraging their use through bad examples that show your lack of basic understanding towards them.
First of all a well designed reusable module would use a better namespace than something as simple and useless as "Gizmo". They are plenty of ways of handling this, for example if you look at the Java* world you'll notice the norm here is the "reverse URL" way, ie. all Apache Foundation projects are contained in "org.apache.<project name>" namespaces (in PHP the :: is used as namespace seperator so the PHP equivalent would be "org::apache::<project name>") Also keep in mind that a project can have multiple namespaces inside it, which is not obligatory but provides an additionnal way of cleanly seperating code in distinct units.
Secondly, when using tokens from external namespaces, you are meant to export them through the "use" keyword at the top of your code. This allows you to maintain tight control over external interfaces. It also avoids repeating the same "base name" of your class over and over and over in your code, which makes it cleaner and easier to refactor.
Namespaces were the missing link preventing PHP 5 from becoming a real object oriented language. Even if YOU are not interested in using them in your projects, you may want to not be so quick at dissing them.
* Java namespaces go by the cheesy name of "packages" but they basically work as you'd expect namespaces to do in any other language
Valeriu Palo
03-May-2008 10:57
03-May-2008 10:57
I see nothing wrong with this implementation.
Having free code disallowed in namespaces is (I think) a good thing. If namespaces are used in a script, it is quite clear that the script is strongly object oriented, and thus the usage of variables and code that are "raw" in a namespace is nothing less than weird! That functionlity would much better fit inside a class (or a Singleton?). It is the same principle behind what makes global variables a bad choice.
As far as the naming conventions go, a namespace is only meant to help you "isolate" your constructs from what others might accidentally create and then clash with your scripts. Of course one could potentially use the same identifiers as another but the point is that such an act would be intentional and not accidental! When you create a library, you might want to put everything inside a namespace that is intuitively connected to you or your project and not something that someone else might be inclined to use.
Alas, this truly has NOTHING to do with the language!
Anonymous
01-Apr-2008 12:11
01-Apr-2008 12:11
@ RS: Also, you can specify how your __autoload() function looks for the files. That way another users namespace classes cannot overwrite yours unless they replace your file specifically.
someone3x7 at hotmail dot com
05-Mar-2008 11:57
05-Mar-2008 11:57
RS, I've mostly used namespaces for Read-ability. And to collect those few loose low level functions that, while necessary, have no business in an object with the classes thier almost related too. Its also good to keep the Global namespace scope clean of unnecesary symbols, which in larger projects affects performance slightly and makes debugging easier. I'm sure I could go on, yet the Read-ability should be enough for most.
FB
28-Feb-2008 04:05
28-Feb-2008 04:05
RS wrote on 27-Feb-2008 07:31:
"I don't see how this implementation of namespaces gives you anything you didn't already have.
Let's say someone is writing a set of classes to handle gizmos... most developers would write something like:
<?php
class GizmoBird() {
}
class GizmoPlane() {
}
?>
Now with namespaces, this would look like:
<?php
namespace Gizmo;
class Bird() {
}
class Plane() {
}
?>
But this doesn't really help you isolate your classes any better. someone else could still write another set of classes with the same namespace, and Gizmo::Bird would clash with another developer's Gizmo::Bird, in the exact same way that GizmoBird would clash with another developer's GizmoBird.
So effectively, all you've done is add a couple of colons to the classnames...
I honestly hope developers in general don't start using this..."
Let's suppose that your company would do this in java, you create the package com.rs.gizmo and put your classes Bird and Plane into it. Then another developer could stuck other classes into your package.... you see what I mean? it will always be the same thing in php, java c#, c++, etc....
Putting classes in the wrong namespace is not language's fault...
RS
27-Feb-2008 02:31
27-Feb-2008 02:31
I don't see how this implementation of namespaces gives you anything you didn't already have.
Let's say someone is writing a set of classes to handle gizmos... most developers would write something like:
<?php
class GizmoBird() {
}
class GizmoPlane() {
}
?>
Now with namespaces, this would look like:
<?php
namespace Gizmo;
class Bird() {
}
class Plane() {
}
?>
But this doesn't really help you isolate your classes any better. someone else could still write another set of classes with the same namespace, and Gizmo::Bird would clash with another developer's Gizmo::Bird, in the exact same way that GizmoBird would clash with another developer's GizmoBird.
So effectively, all you've done is add a couple of colons to the classnames...
I honestly hope developers in general don't start using this...
someone3x7 at hotmail dot com
20-Feb-2008 01:38
20-Feb-2008 01:38
"but no free code."
Seems can not declare variables in the namespace due to this limitation. Can hardly call it a namespace as is. This with other limitations in php 5.2 sometimes there is need to abuse the global namespace. I'd much rather this issue were resolved rather than ask that php be practically rewritten for true OOP.