MOON
Server: Apache/2.2.31 (Unix) mod_ssl/2.2.31 OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4
System: Linux csr818.wilogic.com 2.6.18-419.el5xen #1 SMP Fri Feb 24 22:50:37 UTC 2017 x86_64
User: digitals (531)
PHP: 5.4.45
Disabled: NONE
Upload Files
File: //usr/local/ssl/local/share/man/man3/DBIx::MyParsePP::Token.3
.\" Automatically generated by Pod::Man v1.37, Pod::Parser v1.32
.\"
.\" Standard preamble:
.\" ========================================================================
.de Sh \" Subsection heading
.br
.if t .Sp
.ne 5
.PP
\fB\\$1\fR
.PP
..
.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.  | will give a
.\" real vertical bar.  \*(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-|\(bv\*(Tr
.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" ''
'br\}
.\"
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD.  Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
.if \nF \{\
.    de IX
.    tm Index:\\$1\t\\n%\t"\\$2"
..
.    nr % 0
.    rr F
.\}
.\"
.\" For nroff, turn off justification.  Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.hy 0
.if n .na
.\"
.\" 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 "DBIx::MyParsePP::Token 3"
.TH DBIx::MyParsePP::Token 3 "2007-08-15" "perl v5.8.8" "User Contributed Perl Documentation"
.SH "NAME"
DBIx::MyParsePP::Token \- Lexical tokens extracted by DBIx::MyParsePP::Lexer
.SH "SYNOPSIS"
.IX Header "SYNOPSIS"
Please see the example under \f(CW\*(C`DBIx::MyParsePP::Lexer\*(C'\fR
.SH "METHODS"
.IX Header "METHODS"
\&\f(CW\*(C`new($type, $value)\*(C'\fR creates a new Token object.
.PP
\&\f(CW\*(C`type()\*(C'\fR or \f(CW\*(C`getType()\*(C'\fR returns the type of the Token, as string.
.PP
\&\f(CW\*(C`value()\*(C'\fR or \f(CW\*(C`getValue()\*(C'\fR returns the value of the Token.
.PP
\&\f(CW\*(C`setType($new_type)\*(C'\fR and \f(CW\*(C`setValue($new_value)\*(C'\fR can be used to manipulate the Token.
.PP
\&\f(CW\*(C`toString()\*(C'\fR returns the value of the token, quoted if necessary, as it would appear in a \s-1SQL\s0 statement. A leading
space is added for most tokens in order to facilitate chaining tokens into a larger statement.
.SH "TOKEN TYPES"
.IX Header "TOKEN TYPES"
Token types are returned as strings, to avoid possible confusion between integer values of constants and tokens whose type
is equal to their value. The following types are used by MySQL:
.PP
.Vb 1
\&        "IDENT", "IDENT_QUOTED" - database, table or field identifiers or portions thereof.
.Ve
.PP
.Vb 1
\&        "TEXT_STRING", "NCHAR_STRING" - strings in the form 'aaa' and N'aaa'
.Ve
.PP
.Vb 1
\&        "HEX_NUM", "BIN_NUM" - numbers in the form x'ffff' and b'010101'
.Ve
.PP
.Vb 1
\&        "DECIMAL_NUM", "NUM", "LONG_NUM", "ULONGLONG_NUM" - integers of various lengths
.Ve
.PP
.Vb 1
\&        "FLOAT_NUM" - floating-point numbers in scientific notation, e.g -32032.6809e+10
.Ve
.PP
.Vb 1
\&        "UNDERSCORE_CHARSET" - charset modifier before literal string, eg. _utf8
.Ve
.PP
.Vb 1
\&        "LEX_HOSTNAME" -
.Ve
.PP
.Vb 1
\&        "SET_VAR" - the variable assignment operator :=
.Ve
.PP
Function names and \s-1SQL\s0 constructs are returned mostly as strings ending in \f(CW\*(C`_SYM"\*(C'\fR. The complete list can be found in
\&\f(CW\*(C`DBIx::MyParsePP::Symbols\*(C'\fR. Some functions are returned as \f(CW"FUNC_ARG1"\fR, \f(CW"FUNC_ARG2"\fR or \f(CW"FUNC_ARG3"\fR, signifying
the number of arguments the function expects. In this case, the actual name of the function can be obtained by calling
\&\f(CW\*(C`getValue()\*(C'\fR.
.PP
The rules that determine which type of \f(CW"NUM"\fR is returned can be found in \f(CW\*(C`DBIx::MyParsePP::Lexer::int_token()\*(C'\fR