.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" Set up some character translations and predefined strings. \*(-- will .\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left .\" double quote, and \*(R" will give a right double quote. \*(C+ will .\" give a nicer C++. Capital omega is used to do unbreakable dashes and .\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, .\" nothing in troff, for use with C<>. .tr \(*W- .ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' .ie n \{\ . ds -- \(*W- . ds PI pi . if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch . if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch . ds L" "" . ds R" "" . ds C` "" . ds C' "" 'br\} .el\{\ . ds -- \|\(em\| . ds PI \(*p . ds L" `` . ds R" '' . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is turned on, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{ . if \nF \{ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). .\" Fear. Run. Save yourself. No user-serviceable parts. . \" fudge factors for nroff and troff .if n \{\ . ds #H 0 . ds #V .8m . ds #F .3m . ds #[ \f1 . ds #] \fP .\} .if t \{\ . ds #H ((1u-(\\\\n(.fu%2u))*.13m) . ds #V .6m . ds #F 0 . ds #[ \& . ds #] \& .\} . \" simple accents for nroff and troff .if n \{\ . ds ' \& . ds ` \& . ds ^ \& . ds , \& . ds ~ ~ . ds / .\} .if t \{\ . ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u" . ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u' . ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u' . ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u' . ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u' . ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u' .\} . \" troff and (daisy-wheel) nroff accents .ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V' .ds 8 \h'\*(#H'\(*b\h'-\*(#H' .ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#] .ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H' .ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u' .ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#] .ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#] .ds ae a\h'-(\w'a'u*4/10)'e .ds Ae A\h'-(\w'A'u*4/10)'E . \" corrections for vroff .if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u' .if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u' . \" for low resolution devices (crt and lpr) .if \n(.H>23 .if \n(.V>19 \ \{\ . ds : e . ds 8 ss . ds o a . ds d- d\h'-1'\(ga . ds D- D\h'-1'\(hy . ds th \o'bp' . ds Th \o'LP' . ds ae ae . ds Ae AE .\} .rm #[ #] #H #V #F C .\" ======================================================================== .\" .IX Title "XML::Easy::Syntax 3pm" .TH XML::Easy::Syntax 3pm "2014-08-15" "perl v5.20.0" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH "NAME" XML::Easy::Syntax \- excruciatingly correct XML syntax .SH "SYNOPSIS" .IX Header "SYNOPSIS" .Vb 3 \& use XML::Easy::Syntax qw($xml10_name_rx); \& if($name =~ /\eA$xml10_name_rx\ez/o) { ... \& # and many other regular expressions .Ve .SH "DESCRIPTION" .IX Header "DESCRIPTION" This module supplies Perl regular expressions describing the grammar of \&\s-1XML 1.0. \s0 This is intended to support doing irregular things with \s-1XML,\s0 rather than for normal parsing. .PP These regular expressions encompass the entire \s-1XML\s0 grammar except for document type declarations and DTDs. This document assumes general familiarity with \s-1XML.\s0 .SH "REGULAR EXPRESSIONS" .IX Header "REGULAR EXPRESSIONS" Each of these regular expressions corresponds precisely to one of the productions in the \s-1EBNF\s0 grammar in the \s-1XML 1.0\s0 specification. Well-formedness constraints that are not expressed in the \s-1EBNF\s0 are \&\fInot\fR checked by the regular expressions; these are noted in the documentation below. The regular expressions do not include any anchors, so to check whether an entire string matches a production you must supply the anchors yourself. .SS "Syntax pieces" .IX Subsection "Syntax pieces" .ie n .IP "$xml10_char_rx" 4 .el .IP "\f(CW$xml10_char_rx\fR" 4 .IX Item "$xml10_char_rx" Any single character that is acceptable to \s-1XML 1.0. \s0 This includes most Unicode characters (up to codepoint 0x10ffff). The excluded codepoints are the sentinels 0xfffe and 0xffff, the surrogate blocks, and most of the C0 control characters (0x00 to 0x1f, except for 0x09 (tab), 0x0a (linefeed/newline), and 0x0d (carriage return)). .Sp It is a rule of \s-1XML\s0 that all characters making up an \s-1XML\s0 document must be in this permitted set. The grammar productions can only match sequences of acceptable characters. This rule is enforced by the regular expressions in this module. .Sp Furthermore, it is a rule that the character data in a document cannot even \fIrepresent\fR a character outside the permitted set. This is expressed as a well-formedness constraint on character references. .ie n .IP "$xml10_s_rx" 4 .el .IP "\f(CW$xml10_s_rx\fR" 4 .IX Item "$xml10_s_rx" Any sequence of one or more acceptable whitespace characters. The whitespace characters, for this purpose, are tab, linefeed/newline, carriage return, and space. Non-ASCII whitespace characters, and the more exotic \s-1ASCII\s0 whitespace characters, do not qualify. .ie n .IP "$xml10_eq_rx" 4 .el .IP "\f(CW$xml10_eq_rx\fR" 4 .IX Item "$xml10_eq_rx" Equals sign, surrounded by optional whitespace. .SS "Names" .IX Subsection "Names" .ie n .IP "$xml10_namestartchar_rx" 4 .el .IP "\f(CW$xml10_namestartchar_rx\fR" 4 .IX Item "$xml10_namestartchar_rx" Any single character that is permitted at the start of a name. The permitted characters are "\fB_\fR\*(L", \*(R"\fB:\fR", and letters (categorised according to Unicode 2.0). .Sp This production is not named in the \s-1XML\s0 specification. .ie n .IP "$xml10_namechar_rx" 4 .el .IP "\f(CW$xml10_namechar_rx\fR" 4 .IX Item "$xml10_namechar_rx" Any single character that is permitted in a name other than at the start. The permitted characters are "\fB.\fR\*(L", \*(R"\fB\-\fR\*(L", \*(R"\fB_\fR\*(L", \*(R"\fB:\fR", and letters, digits, combining characters, and extenders (categorised according to Unicode 2.0). .ie n .IP "$xml10_name_rx" 4 .el .IP "\f(CW$xml10_name_rx\fR" 4 .IX Item "$xml10_name_rx" A name, of the type used to identify element types, attributes, entities, and other things in \s-1XML.\s0 .ie n .IP "$xml10_names_rx" 4 .el .IP "\f(CW$xml10_names_rx\fR" 4 .IX Item "$xml10_names_rx" A space-separated list of one or more names. .ie n .IP "$xml10_nmtoken_rx" 4 .el .IP "\f(CW$xml10_nmtoken_rx\fR" 4 .IX Item "$xml10_nmtoken_rx" A name-like token, much like a name except that the first character is no more restricted than the remaining characters. These tokens play no part in basic \s-1XML\s0 syntax, and in the specification are only used as part of attribute typing. .ie n .IP "$xml10_nmtokens_rx" 4 .el .IP "\f(CW$xml10_nmtokens_rx\fR" 4 .IX Item "$xml10_nmtokens_rx" A space-separated list of one or more name-like tokens. .SS "References" .IX Subsection "References" .ie n .IP "$xml10_charref_rx" 4 .el .IP "\f(CW$xml10_charref_rx\fR" 4 .IX Item "$xml10_charref_rx" A numeric character reference (beginning with "\fB&#\fR\*(L" and ending with \&\*(R"\fB;\fR"). There is a non-syntactic well-formedness constraint: the codepoint is required to be within the Unicode range and to refer to an acceptable character (as discussed at \f(CW$xml10_char_rx\fR). .ie n .IP "$xml10_entityref_rx" 4 .el .IP "\f(CW$xml10_entityref_rx\fR" 4 .IX Item "$xml10_entityref_rx" A general entity reference (beginning with "\fB&\fR\*(L" and ending with \*(R"\fB;\fR"). There are non-syntactic well-formedness constraints: the referenced entity must be declared (possibly implicitly), must not be an unparsed entity, must not contain a recursive reference to itself, and its replacement text must itself be well-formed. .ie n .IP "$xml10_reference_rx" 4 .el .IP "\f(CW$xml10_reference_rx\fR" 4 .IX Item "$xml10_reference_rx" Either a character reference or an entity reference. The well-formedness constraints of both reference types (see above) apply. .SS "Character data" .IX Subsection "Character data" .ie n .IP "$xml10_chardata_rx" 4 .el .IP "\f(CW$xml10_chardata_rx\fR" 4 .IX Item "$xml10_chardata_rx" Ordinary literal character data. This consists of zero or more acceptable charaters, other than the metacharacters "\fB<\fR\*(L" and \*(R"\fB&\fR\*(L", and not including \*(R"\fB]]>\fR" as a subsequence. Such data stands for itself when it appears between the start and end tags of an element, where it can be interspersed with references, \s-1CDATA\s0 sections, comments, and processing instructions. .Sp In the \s-1XML\s0 grammar, character data is parsed, and taken literally, \&\fIafter\fR line endings have been canonicalised (to the newline character). Pre-canonicalisation character data, with variable line endings, will still match this production but should not be interpreted literally. .Sp Beware that a string that does not match this production might parse as two adjacent strings each of which matches. This can happen because of the prohibition on "\fB]]>\fR" being embedded in character data, while the characters of that sequence are acceptable individually. The \s-1XML\s0 grammar does not allow two instances of this production to abut. .ie n .IP "$xml10_cdata_rx" 4 .el .IP "\f(CW$xml10_cdata_rx\fR" 4 .IX Item "$xml10_cdata_rx" Literal character data in a \s-1CDATA\s0 section. This consists of zero or more acceptable charaters, not including "\fB]]>\fR\*(L" as a subsequence. Unlike ordinary literal character data, the characters \*(R"\fB<\fR\*(L" and \&\*(R"\fB&\fR" are not metacharacters here. Such data stands for itself when it appears within a \s-1CDATA\s0 section. .Sp As with ordinary literal character data (see above), this data is meant to be taken literally only after line endings have been canonicalised. Also, as with ordinary literal character data, two instances of this production should not abut. .ie n .IP "$xml10_cdstart_rx" 4 .el .IP "\f(CW$xml10_cdstart_rx\fR" 4 .IX Item "$xml10_cdstart_rx" .PD 0 .ie n .IP "$xml10_cdend_rx" 4 .el .IP "\f(CW$xml10_cdend_rx\fR" 4 .IX Item "$xml10_cdend_rx" .PD The fixed strings "\fB\fR" which begin and finish a \s-1CDATA\s0 section. .ie n .IP "$xml10_cdsect_rx" 4 .el .IP "\f(CW$xml10_cdsect_rx\fR" 4 .IX Item "$xml10_cdsect_rx" A \s-1CDATA\s0 section. This consists of "\fB\fR". .SS "Tags" .IX Subsection "Tags" .ie n .IP "$xml10_attvalue_rx" 4 .el .IP "\f(CW$xml10_attvalue_rx\fR" 4 .IX Item "$xml10_attvalue_rx" A quoted attribute value. This consists of acceptable characters other than "\fB<\fR\*(L", \*(R"\fB&\fR\*(L", and the quote character, interspersed with references, surrounded by matching \*(R"\fB"\fR\*(L" or \*(R"\fB'\fR\*(L" quotes. The well-formedness constraints of references apply, and additionally the replacement text of any referenced entities must not contain any \*(R"\fB<\fR" characters, and it is not permitted to refer to external entities. .ie n .IP "$xml10_attribute_rx" 4 .el .IP "\f(CW$xml10_attribute_rx\fR" 4 .IX Item "$xml10_attribute_rx" A complete attribute, consisting of name, equals sign, and quoted value. The well-formedness constraints of attribute values (pertaining to references) apply. .ie n .IP "$xml10_stag_rx" 4 .el .IP "\f(CW$xml10_stag_rx\fR" 4 .IX Item "$xml10_stag_rx" A start-tag, used to begin an element. This consists of "\fB<\fR\*(L", the element type name, whitespace-separated list of attributes, and \*(R"\fB>\fR". The well-formedness constraints of attribute values (pertaining to references) apply. There is also a well-formedness constraint that attribute names must be unique within the tag. .ie n .IP "$xml10_etag_rx" 4 .el .IP "\f(CW$xml10_etag_rx\fR" 4 .IX Item "$xml10_etag_rx" An end-tag, used to finish an element. This consists of "\fB\fR". .ie n .IP "$xml10_emptyelemtag_rx" 4 .el .IP "\f(CW$xml10_emptyelemtag_rx\fR" 4 .IX Item "$xml10_emptyelemtag_rx" An empty-element tag, used to represent an element with no content. This consists of "\fB<\fR\*(L", the element type name, whitespace-separated list of attributes, and \*(R"\fB/>\fR". The well-formedness constraints of attribute values (pertaining to references) apply. There is also a well-formedness constraint that attribute names must be unique within the tag. (These are the same constraints as for start-tags.) .SS "Non-data content" .IX Subsection "Non-data content" .ie n .IP "$xml10_comment_rx" 4 .el .IP "\f(CW$xml10_comment_rx\fR" 4 .IX Item "$xml10_comment_rx" A comment. This does not contribute to the data content of an \&\s-1XML\s0 document. It consists of "\fB\fR\*(L". It is not permitted for the content to include \*(R"\fB\-\-\fR\*(L" as a subsequence, nor for it to end with \*(R"\fB\-\fR". .ie n .IP "$xml10_pitarget_rx" 4 .el .IP "\f(CW$xml10_pitarget_rx\fR" 4 .IX Item "$xml10_pitarget_rx" A processing instruction target name. This can be any name (the \&\f(CW$xml10_name_rx\fR production) except for "\fBxml\fR" and its case variations. .ie n .IP "$xml10_pi_rx" 4 .el .IP "\f(CW$xml10_pi_rx\fR" 4 .IX Item "$xml10_pi_rx" A processing instruction. This consists of "\fB\fR". A processing instruction does not contribute to the data content of an \s-1XML\s0 document, but is intended to carry metadata regarding how to process it. The instruction is addressed to a particular \s-1XML\s0 processor, or type of processor, identified by the target name, and the content of the instruction is expected to be meaningful only to its target. .Sp No one has ever come up with a good use for processing instructions. They are best shunned. .SS "Recursive structure" .IX Subsection "Recursive structure" .ie n .IP "$xml10_content_rx" 4 .el .IP "\f(CW$xml10_content_rx\fR" 4 .IX Item "$xml10_content_rx" The matter contained within an element (between its start-tag and end-tag). This consists of stretches of ordinary literal character data, interspersed with complete elements (recursively), references, \&\s-1CDATA\s0 sections, processing instructions, and comments, in any order. The well-formedness constraints of references and elements apply. .ie n .IP "$xml10_element_rx" 4 .el .IP "\f(CW$xml10_element_rx\fR" 4 .IX Item "$xml10_element_rx" A complete element. This is either an empty-element tag, or a sequence of start-tag, content, and end-tag. The well-formedness constraints regarding references and attribute uniqueness apply in the empty-element tag or start-tag. In the non-empty form, the content also has well-formedness constraints regarding references and (recursively) contained elements, and there is an additional constraint that the element type name in the end-tag must match that in the start-tag. .SS "\s-1XML\s0 declarations" .IX Subsection "XML declarations" .ie n .IP "$xml10_versionnum_rx" 4 .el .IP "\f(CW$xml10_versionnum_rx\fR" 4 .IX Item "$xml10_versionnum_rx" The version number of the \s-1XML\s0 specification. This is the fixed string "\fB1.0\fR". .ie n .IP "$xml10_versioninfo_rx" 4 .el .IP "\f(CW$xml10_versioninfo_rx\fR" 4 .IX Item "$xml10_versioninfo_rx" The version declaration part of an \s-1XML\s0 declaration. .ie n .IP "$xml10_encname_rx" 4 .el .IP "\f(CW$xml10_encname_rx\fR" 4 .IX Item "$xml10_encname_rx" A character encoding name. This must start with an \s-1ASCII\s0 letter, and contain only \s-1ASCII\s0 letters and digits and "\fB.\fR\*(L", \*(R"\fB_\fR\*(L", and \*(R"\fB\-\fR". .ie n .IP "$xml10_encodingdecl_rx" 4 .el .IP "\f(CW$xml10_encodingdecl_rx\fR" 4 .IX Item "$xml10_encodingdecl_rx" The encoding declaration part of an \s-1XML\s0 declaration. .ie n .IP "$xml10_sddecl_rx" 4 .el .IP "\f(CW$xml10_sddecl_rx\fR" 4 .IX Item "$xml10_sddecl_rx" The standaloneness declaration part of an \s-1XML\s0 declaration. This indicates whether the \s-1XML\s0 document can be correctly interpreted without examining the external part of the \s-1DTD.\s0 .ie n .IP "$xml10_xmldecl_rx" 4 .el .IP "\f(CW$xml10_xmldecl_rx\fR" 4 .IX Item "$xml10_xmldecl_rx" An \s-1XML\s0 declaration, as used at the start of an \s-1XML\s0 document. This consists of "\fB\fR". .ie n .IP "$xml10_textdecl_rx" 4 .el .IP "\f(CW$xml10_textdecl_rx\fR" 4 .IX Item "$xml10_textdecl_rx" A text declaration, as used at the start of an \s-1XML\s0 external parsed entity or external \s-1DTD. \s0 This consists of "\fB\fR". This is very similar to an \s-1XML\s0 declaration, but technically a different item and used in different situations. It is possible, and useful, to construct a declaration which is acceptable both as an \s-1XML\s0 declaration and as a text declaration. .SS "Document structure" .IX Subsection "Document structure" .ie n .IP "$xml10_misc_rx" 4 .el .IP "\f(CW$xml10_misc_rx\fR" 4 .IX Item "$xml10_misc_rx" Non-content item permitted in the prologue and epilogue of a document. This is either a comment, a processing instruction, or a stretch of whitespace. .Sp Beware in using a pattern such as \f(CW\*(C`$xml10_misc_rx*\*(C'\fR. It could match a string of whitespace charaters in many ways, leading to exponential behaviour if it becomes necessary to backtrack. This can be avoided by using the \f(CW$xml10_miscseq_rx\fR pattern (below). .ie n .IP "$xml10_miscseq_rx" 4 .el .IP "\f(CW$xml10_miscseq_rx\fR" 4 .IX Item "$xml10_miscseq_rx" A sequence (possibly empty) of non-content matter permitted in the prologue and epilogue of a document. This can contain comments, processing instructions, and whitespace, in any order. .Sp This production is not named in the \s-1XML\s0 specification. This regular expression should be preferred over \f(CW\*(C`$xml10_misc_rx*\*(C'\fR (which is the direct translation of what appears in the \s-1XML\s0 specification), because this one guarantees to match a particular text in only one way, and is thus able to backtrack cleanly. .ie n .IP "$xml10_prolog_xdtd_rx" 4 .el .IP "\f(CW$xml10_prolog_xdtd_rx\fR" 4 .IX Item "$xml10_prolog_xdtd_rx" Document prologue, except for not permitting a document type declaration. This consists of an optional \s-1XML\s0 declaration followed by any sequence of comments, processing instructions, and whitespace. .ie n .IP "$xml10_document_xdtd_rx" 4 .el .IP "\f(CW$xml10_document_xdtd_rx\fR" 4 .IX Item "$xml10_document_xdtd_rx" A complete \s-1XML\s0 document, except for not permitting a document type declaration. This consists of a non-content prologue, an element (the root element, which can recursively contain other elements), and a non-content epilogue. The well-formedness constraints of elements apply to the root element. .ie n .IP "$xml10_extparsedent_rx" 4 .el .IP "\f(CW$xml10_extparsedent_rx\fR" 4 .IX Item "$xml10_extparsedent_rx" A complete external parsed entity. This consists of an optional text declaration followed by a sequence of content of the same type that is permitted within an element. The well-formedness constraints of element content apply. .SH "BUGS" .IX Header "BUGS" Many of these regular expressions are liable to tickle a serious bug in perl's regexp engine. The bug is that the \f(CW\*(C`*\*(C'\fR and \f(CW\*(C`+\*(C'\fR repeat operators don't always match an unlimited number of repeats: in some cases they are limited to 32767 iterations. Whether this bogus limit applies depends on the complexity of the expression being repeated, whether the string being examined is internally encoded in \s-1UTF\-8,\s0 and the version of perl. In some cases, but not all, a false match failure is preceded by a warning \&\*(L"Complex regular subexpression recursion limit (32766) exceeded\*(R". .PP This bug is present, in various forms, in all perl versions up to at least 5.8.9 and 5.10.0. Pre\-5.10 perls may also overflow their stack space, in similar circumstances, if a resource limit is imposed. .PP There is no known feasible workaround for this perl bug. The regular expressions supplied by this module will therefore, unavoidably, fail to accept some lengthy valid inputs. Where this occurs, though, it is likely that other regular expressions being applied to the same or related input will also suffer the same problem. It is pervasive. Do not rely on this module (or perl) to process long inputs on affected perl versions. .PP This bug does not affect the XML::Easy::Text parser. .SH "SEE ALSO" .IX Header "SEE ALSO" XML::Easy::Text, .SH "AUTHOR" .IX Header "AUTHOR" Andrew Main (Zefram) .SH "COPYRIGHT" .IX Header "COPYRIGHT" Copyright (C) 2008, 2009 PhotoBox Ltd .PP Copyright (C) 2009, 2010, 2011 Andrew Main (Zefram) .SH "LICENSE" .IX Header "LICENSE" This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself.