.\" -*- mode: troff; coding: utf-8 -*-
.\" Automatically generated by Pod::Man 5.01 (Pod::Simple 3.43)
.\"
.\" 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
..
.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
.ie n \{\
.    ds C` ""
.    ds C' ""
'br\}
.el\{\
.    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 >0, 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
.\" ========================================================================
.\"
.IX Title "PPI::Token::End 3pm"
.TH PPI::Token::End 3pm 2024-03-16 "perl v5.38.2" "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
PPI::Token::End \- Completely useless content after the _\|_END_\|_ tag
.SH INHERITANCE
.IX Header "INHERITANCE"
.Vb 3
\&  PPI::Token::End
\&  isa PPI::Token
\&          isa PPI::Element
.Ve
.SH DESCRIPTION
.IX Header "DESCRIPTION"
If you've read PPI::Token::Whitespace, you should understand by now
the concept of documents "floating in a sea of PPI::Token::Whitespace".
.PP
Well it doesn't after the _\|_END_\|_ tag.
.PP
Once you _\|_END_\|_, it's all over. Anything after that tag isn't even fit
to be called whitespace. It just simply doesn't exist as far as perl
(the interpreter) is concerned.
.PP
That's not to say there isn't useful content. Most often people use
the _\|_END_\|_ tag to hide POD content, so that perl never has to see it,
and presumably providing some small speed up.
.PP
That's fine. PPI likes POD. Any POD after the _\|_END_\|_ tag is parsed
into valid PPI::Token::Pod tags as normal. \fBThis\fR class, on the
other hand, is for "what's after _\|_END_\|_ when it isn't POD".
.PP
Basically, the completely worthless bits of the file :)
.SH METHODS
.IX Header "METHODS"
This class has no method beyond what is provided by its PPI::Token and
PPI::Element parent classes.
.SH SUPPORT
.IX Header "SUPPORT"
See the support section in the main module.
.SH AUTHOR
.IX Header "AUTHOR"
Adam Kennedy <adamk@cpan.org>
.SH COPYRIGHT
.IX Header "COPYRIGHT"
Copyright 2001 \- 2011 Adam Kennedy.
.PP
This program is free software; you can redistribute
it and/or modify it under the same terms as Perl itself.
.PP
The full text of the license can be found in the
LICENSE file included with this module.