DomElement::tagname
Integer overflow for 64 bit platform
If PHP encounters a number beyond the bounds of the integer type, it will be interpreted as a float.
This above general rule differs depending on whether a 32 bit or 64 bit platform is used, which is described as follows.
Platform:32 bit,Range: -2^31-1 to 2^31-1,Numbers:-2147483647 to 2147483647
Platform:64 bit,Range: -2^63-1 and 2^63 -1,Numbers:-9223372036854775807 to 9223372036854775807
<?php
$large_number=9223372036854775807;
var_dump($large_number);
// output: int(9223372036854775807)
$large_number = 9223372036854775808;
var_dump($large_number);
// output: float(9.2233720368548E+18) as 9223372036854775808
//2^64-1 is 18446744073709551615
var_dump(0xffffffffffffffff);
// output: float(1.844674407371E+19) as 18446744073709551615
?>
DomNode::add_namespace
(PHP 4 >= 4.3.0)
DomNode::add_namespace — Ajoute une déclaration d'espace de nom à un noeud
Description
bool DOMNode::add_namespace
( string
$uri
, string $prefix
)Cette méthode ajoute une déclaration de nom à un noeud.
Note:
Cette méthode ne fait pas partie des spécifications DOM.
Liste de paramètres
-
uri -
L'espace de nom URI du noeud.
-
prefix -
Le préfixe de l'espace de nom du noeud.
Valeurs de retour
Cette fonction retourne TRUE en cas de
succès ou FALSE si une erreur survient.
Migration vers PHP 5
Vous pouvez spécifier l'espace de nom URI et le préfixe de DOMElement ou de DOMAttr à la création en utilisant DOMDocument::createElementNS ou DOMDocument::createAttributeNS.
Note:
Rappelez-vous qu'un attribut n'hérite pas son espace de nom à partir de l'élément dont il est attaché.
add a note
User Contributed Notes
DomNode::add_namespace
vivekanandan8 at yahoo dot com
18-Mar-2009 10:01
tkearns at fastmail dot fm
17-Sep-2003 02:02
<?php
// EXAMPLE USING PHP 4.3.3
$objDoc = domxml_new_doc("1.0");
$ndRoot = $objDoc->create_element("root");
$ndRoot = $objDoc->append_child($ndRoot);
$ndRoot->set_namespace("foo/the/bar");
// using ramdom prefix, produces something like
// <a3767:root xmlns:a3767="foo/the/bar"/>
$ndRoot->set_namespace("yet/another/namespace","yan");
// modifies the existing prefix (again) produces something like
// <yan:root xmlns:a3767="foo/the/bar" xmlns:yan="yet/another/namespace"/>
$ndRoot->set_namespace("yet/another/namespace","foo");
// attempt to use the same ns id has again no effect. element is un-touched
// <yan:root xmlns:a3767="foo/the/bar" xmlns:yan="yet/another/namespace"/>
$ndRoot->set_namespace("new/ns/no/prefix");
// munges the existing element prefix again as well as adding declaration
// <a1757:root
// xmlns:a3767="foo/the/bar"
// xmlns:yan="yet/another/namespace"
// xmlns:a1757="new/ns/no/prefix"
// />
/*
It seems that the only way to add a DEFAULT namespace to a node (without
affecting the current prefix), is to use set_attribute("xmlns",$ndId).
*/
$ndRoot->set_attribute("xmlns","default/ns/no/prefix");
// now we have
// <a1757:root
// xmlns:a3767="foo/the/bar"
// xmlns:yan="yet/another/namespace"
// xmlns:a1757="new/ns/no/prefix"
// xmlns="default/ns/no/prefix"
// />
/*
Note that namespace declarations inserted using set_namespace are not classed as
attributes, so they do not show up in an attribute list. Since we set our
default namespace using the set_attribute() method, it is the only one that will
show up.
*/
var_dump($ndRoot->attributes());
// see that only the defaul namespace is returned because it is of type
// "domattribute" because we set it with an attribute method.
$ndRoot->set_attribute("xmlns:pfx","non/default/with/prefix");
// now we have
// <a1757:root
// xmlns:a3767="foo/the/bar"
// xmlns:yan="yet/another/namespace"
// xmlns:a1757="new/ns/no/prefix"
// xmlns="default/ns/no/prefix"
// xmlns:pfx="non/default/with/prefix"
// />
/*
Any XML processor still regards it as a namespace declaration the same way
they recognise the other namespaces we declared. Problem for us is that we
cannot ascertain the existing namespace declarations on any element if they are
not declared using set_attribute. Furthermore, external files imported into
DOMXML objects do NOT have their namespace declarations detected as attributes -
and rightly so. But the problem arises that now there is no way to detect these
declarations.
*/
var_dump($ndRoot->attributes());
// Our new "xmlns:pfx" *attribute* now shows up because we set it with an
// attribute method and it is of type "domattribute". So what of our namespace
// declarations using set_namespace() then? Do they have a type?
/*
Well there doesn't seem to be any other dom type where our declarations can
reside. This is problably the reason why we have no way of detecting them.
It's important to note that when parsing in external XML files, the prefixed
namespace declarations do NOT show up in the list of attribute nodes.
*/
/*
I would also argue that destroying the existing element prefix by forcing the
[re]population of it with a new one when using set_namespace() should be
considdered "unexpected behaviour". If the user doesn not supply a prefix, then
it should be added as the default namespace (with no prefix).
Using set_attribute() is a workaround to the "problem" and not a solution.
*/
/*
The behaviour of set_namespace() is not the biggest problem though.
Inability to detect existing namespace declarations is. How do I find out if
a namespace with id of "yet/another/namespace" has been declared in this
element? The answer is I can't. And if I could, I would also want to know what
prefix it is using.
*/
echo htmlentities($objDoc->dump_mem(true));
?>