NAME
HTML::DOM::Exception - The Exception interface for HTML::DOM
VERSION
Version 0.058
SYNOPSIS
use HTML::DOM::Exception 'INVALID_CHARACTER_ERR';
eval {
die new HTML::DOM::Exception
INVALID_CHARACTER_ERR,
'Only ASCII characters allowed!'
};
$@ == INVALID_CHARACTER_ERR; # true
print $@; # prints "Only ASCII characters allowed!\n";
DESCRIPTION
This module implementations the W3C's DOMException and EventException interfaces. HTML::DOM::Exception objects stringify to the message passed to the constructer and numify to the error number (see below, under 'EXPORTS').
METHODS
- $errr = new HTML::DOM::Exception $type, $message
-
This class method creates a new exception object.
$type
is expected to be an integer (you can use the constants listed under 'EXPORTS').$message
is the error message. - $errr->code
-
Returns the error code. Same as
0+$errr
.
EXPORTS
The following constants are optionally exported. The descriptions are copied from the DOM spec.
- INDEX_SIZE_ERR (1)
-
If index or size is negative, or greater than the allowed value
- DOMSTRING_SIZE_ERR (2)
-
If the specified range of text does not fit into a DOMString
- HIERARCHY_REQUEST_ERR (3)
-
If any node is inserted somewhere it doesn't belong
- WRONG_DOCUMENT_ERR (4)
-
If a node is used in a different document than the one that created it (that doesn't support it)
- INVALID_CHARACTER_ERR (5)
-
If an invalid character is specified, such as in a name.
- NO_DATA_ALLOWED_ERR (6)
-
If data is specified for a node which does not support data
- NO_MODIFICATION_ALLOWED_ERR (7)
-
If an attempt is made to modify an object where modifications are not allowed
- NOT_FOUND_ERR (8)
-
If an attempt was made to reference a node in a context where it does not exist
- NOT_SUPPORTED_ERR (9)
-
If the implementation does not support the type of object requested
- INUSE_ATTRIBUTE_ERR (10)
-
If an attempt is made to add an attribute that is already inuse elsewhere
- INVALID_STATE_ERR (11)
-
If an attempt is made to use an object that is not, or is no longer, usable
- SYNTAX_ERR (12)
-
If an invalid or illegal string is specified
- INVALID_MODIFICATION_ERR (13)
-
If an attempt is made to modify the type of the underlying object
- NAMESPACE_ERR (14)
-
If an attempt is made to create or change an object in a way which is incorrect with regard to namespaces
- INVALID_ACCESS_ERR (15)
-
If a parameter or an operation is not supported by the underlying object
- UNSPECIFIED_EVENT_TYPE_ERR (0)
-
If the Event's type was not specified by initializing the event before the method was called. Specification of the Event's type as null or an empty string will also trigger this exception.
SEE ALSO
1 POD Error
The following errors were encountered while parsing the POD:
- Around line 117:
You forgot a '=back' before '=head1'