Amiga Magazin: Amiga-CD 1996 July/AMIGA_1996_7.BIN/ausgabe_7_96/pd-programmierung/perl5_002bin.lha/man/catp/perldata.0

Text File | 1996-03-02 | 42KB | 727 lines

PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


NNNNAAAAMMMMEEEE
       perldata - Perl data types

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
       VVVVaaaarrrriiiiaaaabbbblllleeee nnnnaaaammmmeeeessss

       Perl has three data structures: scalars, arrays of
       scalars, and associative arrays of scalars, known as
       "hashes".  Normal arrays are indexed by number, starting
       with 0.  (Negative subscripts count from the end.)  Hash
       arrays are indexed by string.

       Scalar values are always named with '$', even when
       referring to a scalar that is part of an array.  It works
       like the English word "the".  Thus we have:

           $$$$ddddaaaayyyyssss               #### tttthhhheeee ssssiiiimmmmpppplllleeee ssssccccaaaallllaaaarrrr vvvvaaaalllluuuueeee """"ddddaaaayyyyssss""""
           $$$$ddddaaaayyyyssss[[[[22228888]]]]           #### tttthhhheeee 22229999tttthhhh eeeelllleeeemmmmeeeennnntttt ooooffff aaaarrrrrrrraaaayyyy @@@@ddddaaaayyyyssss
           $$$$ddddaaaayyyyssss{{{{''''FFFFeeeebbbb''''}}}}        #### tttthhhheeee ''''FFFFeeeebbbb'''' vvvvaaaalllluuuueeee ffffrrrroooommmm hhhhaaaasssshhhh %%%%ddddaaaayyyyssss
           $$$$####ddddaaaayyyyssss              #### tttthhhheeee llllaaaasssstttt iiiinnnnddddeeeexxxx ooooffff aaaarrrrrrrraaaayyyy @@@@ddddaaaayyyyssss

       but entire arrays or array slices are denoted by '@',
       which works much like the word "these" or "those":

           @@@@ddddaaaayyyyssss               #### (((($$$$ddddaaaayyyyssss[[[[0000]]]],,,, $$$$ddddaaaayyyyssss[[[[1111]]]],,,,............ $$$$ddddaaaayyyyssss[[[[nnnn]]]]))))
           @@@@ddddaaaayyyyssss[[[[3333,,,,4444,,,,5555]]]]        #### ssssaaaammmmeeee aaaassss @@@@ddddaaaayyyyssss[[[[3333........5555]]]]
           @@@@ddddaaaayyyyssss{{{{''''aaaa'''',,,,''''cccc''''}}}}      #### ssssaaaammmmeeee aaaassss (((($$$$ddddaaaayyyyssss{{{{''''aaaa''''}}}},,,,$$$$ddddaaaayyyyssss{{{{''''cccc''''}}}}))))

       and entire hashes are denoted by '%':

           %%%%ddddaaaayyyyssss               #### ((((kkkkeeeeyyyy1111,,,, vvvvaaaallll1111,,,, kkkkeeeeyyyy2222,,,, vvvvaaaallll2222 ............))))

       In addition, subroutines are named with an initial '&',
       though this is optional when it's otherwise unambiguous
       (just as "do" is often redundant in English).  Symbol
       table entries can be named with an initial '*', but you
       don't really care about that yet.

       Every variable type has its own namespace.  You can,
       without fear of conflict, use the same name for a scalar
       variable, an array, or a hash (or, for that matter, a
       filehandle, a subroutine name, or a label).  This means
       that $$$$ffffoooooooo and @@@@ffffoooooooo are two different variables.  It also
       means that $$$$ffffoooooooo[[[[1111]]]] is a part of @@@@ffffoooooooo, not a part of $$$$ffffoooooooo.
       This may seem a bit weird, but that's okay, because it is
       weird.

       Since variable and array references always start with '$',
       '@', or '%', the "reserved" words aren't in fact reserved
       with respect to variable names.  (They ARE reserved with
       respect to labels and filehandles, however, which don't
       have an initial special character.  You can't have a
       filehandle named "log", for instance.  Hint: you could say
       ooooppppeeeennnn((((LLLLOOOOGGGG,,,,''''llllooooggggffffiiiilllleeee'''')))) rather than ooooppppeeeennnn((((lllloooogggg,,,,''''llllooooggggffffiiiilllleeee'''')))).



30/Jan/96                perl 5.002 with                        1





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


       Using uppercase filehandles also improves readability and
       protects you from conflict with future reserved words.)
       Case _I_S significant--"FOO", "Foo" and "foo" are all
       different names.  Names that start with a letter or
       underscore may also contain digits and underscores.

       It is possible to replace such an alphanumeric name with
       an expression that returns a reference to an object of
       that type.  For a description of this, see the _p_e_r_l_r_e_f
       manpage.

       Names that start with a digit may only contain more
       digits.  Names which do not start with a letter,
       underscore,  or digit are limited to one character, e.g.
       $$$$%%%% or $$$$$$$$.  (Most of these one character names have a
       predefined significance to Perl.  For instance, $$$$$$$$ is the
       current process id.)

       CCCCoooonnnntttteeeexxxxtttt

       The interpretation of operations and values in Perl
       sometimes depends on the requirements of the context
       around the operation or value.  There are two major
       contexts: scalar and list.  Certain operations return list
       values in contexts wanting a list, and scalar values
       otherwise.  (If this is true of an operation it will be
       mentioned in the documentation for that operation.)  In
       other words, Perl overloads certain operations based on
       whether the expected return value is singular or plural.
       (Some words in English work this way, like "fish" and
       "sheep".)

       In a reciprocal fashion, an operation provides either a
       scalar or a list context to each of its arguments.  For
       example, if you say

           iiiinnnntttt(((( <<<<SSSSTTTTDDDDIIIINNNN>>>> ))))

       the integer operation provides a scalar context for the
       <STDIN> operator, which responds by reading one line from
       STDIN and passing it back to the integer operation, which
       will then find the integer value of that line and return
       that.  If, on the other hand, you say

           ssssoooorrrrtttt(((( <<<<SSSSTTTTDDDDIIIINNNN>>>> ))))

       then the sort operation provides a list context for
       <STDIN>, which will proceed to read every line available
       up to the end of file, and pass that list of lines back to
       the sort routine, which will then sort those lines and
       return them as a list to whatever the context of the sort
       was.

       Assignment is a little bit special in that it uses its



30/Jan/96                perl 5.002 with                        2





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


       left argument to determine the context for the right
       argument.  Assignment to a scalar evaluates the righthand
       side in a scalar context, while assignment to an array or
       array slice evaluates the righthand side in a list
       context.  Assignment to a list also evaluates the
       righthand side in a list context.

       User defined subroutines may choose to care whether they
       are being called in a scalar or list context, but most
       subroutines do not need to care, because scalars are
       automatically interpolated into lists.  See the wwwwaaaannnnttttaaaarrrrrrrraaaayyyy
       entry in the _p_e_r_l_f_u_n_c manpage.

       SSSSccccaaaallllaaaarrrr vvvvaaaalllluuuueeeessss

       All data in Perl is a scalar or an array of scalars or a
       hash of scalars.  Scalar variables may contain various
       kinds of singular data, such as numbers, strings, and
       references.  In general, conversion from one form to
       another is transparent.  (A scalar may not contain
       multiple values, but may contain a reference to an array
       or hash containing multiple values.)  Because of the
       automatic conversion of scalars, operations and functions
       that return scalars don't need to care (and, in fact,
       can't care) whether the context is looking for a string or
       a number.

       Scalars aren't necessarily one thing or another.  There's
       no place to declare a scalar variable to be of type
       "string", or of type "number", or type "filehandle", or
       anything else.  Perl is a contextually polymorphic
       language whose scalars can be strings, numbers, or
       references (which includes objects).  While strings and
       numbers are considered the pretty much same thing for
       nearly all purposes, references are strongly-typed
       uncastable pointers with built-in reference-counting and
       destructor invocation.

       A scalar value is interpreted as TRUE in the Boolean sense
       if it is not the null string or the number 0 (or its
       string equivalent, "0").  The Boolean context is just a
       special kind of scalar context.

       There are actually two varieties of null scalars: defined
       and undefined.  Undefined null scalars are returned when
       there is no real value for something, such as when there
       was an error, or at end of file, or when you refer to an
       uninitialized variable or element of an array.  An
       undefined null scalar may become defined the first time
       you use it as if it were defined, but prior to that you
       can use the _d_e_f_i_n_e_d_(_) operator to determine whether the
       value is defined or not.

       To find out whether a given string is a valid non-zero



30/Jan/96                perl 5.002 with                        3





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


       number, it's usually enough to test it against both
       numeric 0 and also lexical "0" (although this will cause
       ----wwww noises).  That's because strings that aren't numbers
       count as 0, just as the do in _a_w_k:

           iiiiffff (((($$$$ssssttttrrrr ======== 0000 &&&&&&&& $$$$ssssttttrrrr nnnneeee """"0000""""))))  {{{{
               wwwwaaaarrrrnnnn """"TTTThhhhaaaatttt ddddooooeeeessssnnnn''''tttt llllooooooookkkk lllliiiikkkkeeee aaaa nnnnuuuummmmbbbbeeeerrrr"""";;;;
           }}}}

       That's usually preferable because otherwise you won't
       treat IEEE notations like NNNNaaaaNNNN or IIIInnnnffffiiiinnnniiiittttyyyy properly.  At
       other times you might prefer to use a regular expression
       to check whether data is numeric.  See the _p_e_r_l_r_e manpage
       for details on regular expressions.

           wwwwaaaarrrrnnnn """"hhhhaaaassss nnnnoooonnnnddddiiiiggggiiiittttssss""""        iiiiffff     ////\\\\DDDD////;;;;
           wwwwaaaarrrrnnnn """"nnnnooootttt aaaa wwwwhhhhoooolllleeee nnnnuuuummmmbbbbeeeerrrr""""   uuuunnnnlllleeeessssssss ////^^^^\\\\dddd++++$$$$////;;;;
           wwwwaaaarrrrnnnn """"nnnnooootttt aaaannnn iiiinnnntttteeeeggggeeeerrrr""""       uuuunnnnlllleeeessssssss ////^^^^[[[[++++----]]]]????\\\\dddd++++$$$$////
           wwwwaaaarrrrnnnn """"nnnnooootttt aaaa ddddeeeecccciiiimmmmaaaallll nnnnuuuummmmbbbbeeeerrrr"""" uuuunnnnlllleeeessssssss ////^^^^[[[[++++----]]]]????\\\\dddd++++\\\\....????\\\\dddd****$$$$////
           wwwwaaaarrrrnnnn """"nnnnooootttt aaaa CCCC ffffllllooooaaaatttt""""
               uuuunnnnlllleeeessssssss ////^^^^(((([[[[++++----]]]]????))))((((????====\\\\dddd||||\\\\....\\\\dddd))))\\\\dddd****((((\\\\....\\\\dddd****))))????(((([[[[EEEEeeee]]]](((([[[[++++----]]]]????\\\\dddd++++))))))))????$$$$////;;;;

       The length of an array is a scalar value.  You may find
       the length of array @@@@ddddaaaayyyyssss by evaluating $$$$####ddddaaaayyyyssss, as in ccccsssshhhh.
       (Actually, it's not the length of the array, it's the
       subscript of the last element, since there is (ordinarily)
       a 0th element.)  Assigning to $$$$####ddddaaaayyyyssss changes the length of
       the array.  Shortening an array by this method destroys
       intervening values.  Lengthening an array that was
       previously shortened _N_O _L_O_N_G_E_R recovers the values that
       were in those elements.  (It used to in Perl 4, but we had
       to break this make to make sure destructors were called
       when expected.)  You can also gain some measure of
       efficiency by preextending an array that is going to get
       big.  (You can also extend an array by assigning to an
       element that is off the end of the array.)  You can
       truncate an array down to nothing by assigning the null
       list () to it.  The following are equivalent:

           @@@@wwwwhhhhaaaatttteeeevvvveeeerrrr ==== (((())));;;;
           $$$$####wwwwhhhhaaaatttteeeevvvveeeerrrr ==== $$$$[[[[ ---- 1111;;;;

       If you evaluate a named array in a scalar context, it
       returns the length of the array.  (Note that this is not
       true of lists, which return the last value, like the C
       comma operator.)  The following is always true:

           ssssccccaaaallllaaaarrrr((((@@@@wwwwhhhhaaaatttteeeevvvveeeerrrr)))) ======== $$$$####wwwwhhhhaaaatttteeeevvvveeeerrrr ---- $$$$[[[[ ++++ 1111;;;;

       Version 5 of Perl changed the semantics of $[: files that
       don't set the value of $[ no longer need to worry about
       whether another file changed its value.  (In other words,
       use of $[ is deprecated.)  So in general you can just
       assume that



30/Jan/96                perl 5.002 with                        4





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


           ssssccccaaaallllaaaarrrr((((@@@@wwwwhhhhaaaatttteeeevvvveeeerrrr)))) ======== $$$$####wwwwhhhhaaaatttteeeevvvveeeerrrr ++++ 1111;;;;

       Some programmer choose to use an explcit conversion so
       nothing's left to doubt:

           $$$$eeeelllleeeemmmmeeeennnntttt____ccccoooouuuunnnntttt ==== ssssccccaaaallllaaaarrrr((((@@@@wwwwhhhhaaaatttteeeevvvveeeerrrr))));;;;

       If you evaluate a hash in a scalar context, it returns a
       value which is true if and only if the hash contains any
       key/value pairs.  (If there are any key/value pairs, the
       value returned is a string consisting of the number of
       used buckets and the number of allocated buckets,
       separated by a slash.  This is pretty much only useful to
       find out whether Perl's (compiled in) hashing algorithm is
       performing poorly on your data set.  For example, you
       stick 10,000 things in a hash, but evaluating %%%%HHHHAAAASSSSHHHH in
       scalar context reveals "1/16", which means only one out of
       sixteen buckets has been touched, and presumably contains
       all 10,000 of your items.  This isn't supposed to happen.)

       SSSSccccaaaallllaaaarrrr vvvvaaaalllluuuueeee ccccoooonnnnssssttttrrrruuuuccccttttoooorrrrssss

       Numeric literals are specified in any of the customary
       floating point or integer formats:

           11112222333344445555
           11112222333344445555....66667777
           ....22223333EEEE----11110000
           0000xxxxffffffffffffffff              #### hhhheeeexxxx
           0000333377777777                #### ooooccccttttaaaallll
           4444____222299994444____999966667777____222299996666       #### uuuunnnnddddeeeerrrrlllliiiinnnneeee ffffoooorrrr lllleeeeggggiiiibbbbiiiilllliiiittttyyyy

       String literals are usually delimited by either single or
       double quotes.  They work much like shell quotes:  double-
       quoted string literals are subject to backslash and
       variable substitution; single-quoted strings are not
       (except for "\\\\''''" and "\\\\\\\\").  The usual Unix backslash
       rules apply for making characters such as newline, tab,
       etc., as well as some more exotic forms.  See the qqqqqqqq entry
       in the _p_e_r_l_o_p manpage for a list.

       You can also embed newlines directly in your strings, i.e.
       they can end on a different line than they begin.  This is
       nice, but if you forget your trailing quote, the error
       will not be reported until Perl finds another line
       containing the quote character, which may be much further
       on in the script.  Variable substitution inside strings is
       limited to scalar variables, arrays, and array slices.
       (In other words, identifiers beginning with $ or @,
       followed by an optional bracketed expression as a
       subscript.)  The following code segment prints out "The
       price is $$$$111100000000."





30/Jan/96                perl 5.002 with                        5





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


           $$$$PPPPrrrriiiicccceeee ==== ''''$$$$111100000000'''';;;;    #### nnnnooootttt iiiinnnntttteeeerrrrpppprrrreeeetttteeeedddd
           pppprrrriiiinnnntttt """"TTTThhhheeee pppprrrriiiicccceeee iiiissss $$$$PPPPrrrriiiicccceeee....\\\\nnnn"""";;;;     #### iiiinnnntttteeeerrrrpppprrrreeeetttteeeedddd

       As in some shells, you can put curly brackets around the
       identifier to delimit it from following alphanumerics.  In
       fact, an identifier within such curlies is forced to be a
       string, as is any single identifier within a hash
       subscript.  Our earlier example,

           $$$$ddddaaaayyyyssss{{{{''''FFFFeeeebbbb''''}}}}

       can be written as

           $$$$ddddaaaayyyyssss{{{{FFFFeeeebbbb}}}}

       and the quotes will be assumed automatically.  But
       anything more complicated in the subscript will be
       interpreted as an expression.

       Note that a single-quoted string must be separated from a
       preceding word by a space, since single quote is a valid
       (though deprecated) character in an identifier (see the
       PPPPaaaacccckkkkaaaaggggeeeessss entry in the _p_e_r_l_m_o_d manpage).

       Two special literals are __LINE__ and __FILE__, which
       represent the current line number and filename at that
       point in your program.  They may only be used as separate
       tokens; they will not be interpolated into strings.  In
       addition, the token __END__ may be used to indicate the
       logical end of the script before the actual end of file.
       Any following text is ignored, but may be read via the
       DATA filehandle.  (The DATA filehandle may read data only
       from the main script, but not from any required file or
       evaluated string.)  The two control characters ^D and ^Z
       are synonyms for __END__ (or __DATA__ in a module; see the
       _S_e_l_f_L_o_a_d_e_r manpage for details on __DATA__).

       A word that has no other interpretation in the grammar
       will be treated as if it were a quoted string.  These are
       known as "barewords".  As with filehandles and labels, a
       bareword that consists entirely of lowercase letters risks
       conflict with future reserved words, and if you use the ----wwww
       switch, Perl will warn you about any such words.  Some
       people may wish to outlaw barewords entirely.  If you say

           uuuusssseeee ssssttttrrrriiiicccctttt ''''ssssuuuubbbbssss'''';;;;

       then any bareword that would NOT be interpreted as a
       subroutine call produces a compile-time error instead.
       The restriction lasts to the end of the enclosing block.
       An inner block may countermand this by saying nnnnoooo ssssttttrrrriiiicccctttt
       ''''ssssuuuubbbbssss''''.

       Array variables are interpolated into double-quoted



30/Jan/96                perl 5.002 with                        6





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


       strings by joining all the elements of the array with the
       delimiter specified in the $$$$"""" variable ($LIST_SEPARATOR in
       English), space by default.  The following are equivalent:

           $$$$tttteeeemmmmpppp ==== jjjjooooiiiinnnn(((($$$$"""",,,,@@@@AAAARRRRGGGGVVVV))));;;;
           ssssyyyysssstttteeeemmmm """"eeeecccchhhhoooo $$$$tttteeeemmmmpppp"""";;;;

           ssssyyyysssstttteeeemmmm """"eeeecccchhhhoooo @@@@AAAARRRRGGGGVVVV"""";;;;

       Within search patterns (which also undergo double-quotish
       substitution) there is a bad ambiguity:  Is ////$$$$ffffoooooooo[[[[bbbbaaaarrrr]]]]//// to
       be interpreted as ////$$$${{{{ffffoooooooo}}}}[[[[bbbbaaaarrrr]]]]//// (where [[[[bbbbaaaarrrr]]]] is a
       character class for the regular expression) or as
       ////$$$${{{{ffffoooooooo[[[[bbbbaaaarrrr]]]]}}}}//// (where [[[[bbbbaaaarrrr]]]] is the subscript to array
       @@@@ffffoooooooo)?  If @@@@ffffoooooooo doesn't otherwise exist, then it's
       obviously a character class.  If @@@@ffffoooooooo exists, Perl takes a
       good guess about [[[[bbbbaaaarrrr]]]], and is almost always right.  If it
       does guess wrong, or if you're just plain paranoid, you
       can force the correct interpretation with curly brackets
       as above.

       A line-oriented form of quoting is based on the shell
       "here-doc" syntax.  Following a <<<<<<<< you specify a string to
       terminate the quoted material, and all lines following the
       current line down to the terminating string are the value
       of the item.  The terminating string may be either an
       identifier (a word), or some quoted text.  If quoted, the
       type of quotes you use determines the treatment of the
       text, just as in regular quoting.  An unquoted identifier
       works like double quotes.  There must be no space between
       the <<<<<<<< and the identifier.  (If you put a space it will be
       treated as a null identifier, which is valid, and matches
       the first blank line--see the Merry Christmas example
       below.)  The terminating string must appear by itself
       (unquoted and with no surrounding whitespace) on the
       terminating line.

               pppprrrriiiinnnntttt <<<<<<<<EEEEOOOOFFFF;;;;
           TTTThhhheeee pppprrrriiiicccceeee iiiissss $$$$PPPPrrrriiiicccceeee....
           EEEEOOOOFFFF

               pppprrrriiiinnnntttt <<<<<<<<""""EEEEOOOOFFFF"""";;;;  #### ssssaaaammmmeeee aaaassss aaaabbbboooovvvveeee
           TTTThhhheeee pppprrrriiiicccceeee iiiissss $$$$PPPPrrrriiiicccceeee....
           EEEEOOOOFFFF

               pppprrrriiiinnnntttt <<<<<<<<````EEEEOOOOCCCC````;;;;  #### eeeexxxxeeeeccccuuuutttteeee ccccoooommmmmmmmaaaannnnddddssss
           eeeecccchhhhoooo hhhhiiii tttthhhheeeerrrreeee
           eeeecccchhhhoooo lllloooo tttthhhheeeerrrreeee
           EEEEOOOOCCCC








30/Jan/96                perl 5.002 with                        7





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


               pppprrrriiiinnnntttt <<<<<<<<""""ffffoooooooo"""",,,, <<<<<<<<""""bbbbaaaarrrr"""";;;; #### yyyyoooouuuu ccccaaaannnn ssssttttaaaacccckkkk tttthhhheeeemmmm
           IIII ssssaaaaiiiidddd ffffoooooooo....
           ffffoooooooo
           IIII ssssaaaaiiiidddd bbbbaaaarrrr....
           bbbbaaaarrrr

               mmmmyyyyffffuuuunnnncccc((((<<<<<<<<""""TTTTHHHHIIIISSSS"""",,,, 22223333,,,, <<<<<<<<''''TTTTHHHHAAAATTTT''''''''))));;;;
           HHHHeeeerrrreeee''''ssss aaaa lllliiiinnnneeee
           oooorrrr ttttwwwwoooo....
           TTTTHHHHIIIISSSS
           aaaannnndddd hhhheeeerrrreeee aaaannnnooootttthhhheeeerrrr....
           TTTTHHHHAAAATTTT

       Just don't forget that you have to put a semicolon on the
       end to finish the statement, as Perl doesn't know you're
       not going to try to do this:

               pppprrrriiiinnnntttt <<<<<<<<AAAABBBBCCCC
           111177779999222233331111
           AAAABBBBCCCC
               ++++ 22220000;;;;


       LLLLiiiisssstttt vvvvaaaalllluuuueeee ccccoooonnnnssssttttrrrruuuuccccttttoooorrrrssss

       List values are denoted by separating individual values by
       commas (and enclosing the list in parentheses where
       precedence requires it):

           ((((LLLLIIIISSSSTTTT))))

       In a context not requiring a list value, the value of the
       list literal is the value of the final element, as with
       the C comma operator.  For example,

           @@@@ffffoooooooo ==== ((((''''cccccccc'''',,,, ''''----EEEE'''',,,, $$$$bbbbaaaarrrr))));;;;

       assigns the entire list value to array foo, but

           $$$$ffffoooooooo ==== ((((''''cccccccc'''',,,, ''''----EEEE'''',,,, $$$$bbbbaaaarrrr))));;;;

       assigns the value of variable bar to variable foo.  Note
       that the value of an actual array in a scalar context is
       the length of the array; the following assigns to $$$$ffffoooooooo the
       value 3:

           @@@@ffffoooooooo ==== ((((''''cccccccc'''',,,, ''''----EEEE'''',,,, $$$$bbbbaaaarrrr))));;;;
           $$$$ffffoooooooo ==== @@@@ffffoooooooo;;;;                #### $$$$ffffoooooooo ggggeeeettttssss 3333

       You may have an optional comma before the closing
       parenthesis of an list literal, so that you can say:






30/Jan/96                perl 5.002 with                        8





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


           @@@@ffffoooooooo ==== ((((
               1111,,,,
               2222,,,,
               3333,,,,
           ))));;;;

       LISTs do automatic interpolation of sublists.  That is,
       when a LIST is evaluated, each element of the list is
       evaluated in a list context, and the resulting list value
       is interpolated into LIST just as if each individual
       element were a member of LIST.  Thus arrays lose their
       identity in a LIST--the list

           ((((@@@@ffffoooooooo,,,,@@@@bbbbaaaarrrr,,,,&&&&SSSSoooommmmeeeeSSSSuuuubbbb))))

       contains all the elements of @@@@ffffoooooooo followed by all the
       elements of @@@@bbbbaaaarrrr, followed by all the elements returned by
       the subroutine named SomeSub when it's called in a list
       context.  To make a list reference that does _N_O_T
       interpolate, see the _p_e_r_l_r_e_f manpage.

       The null list is represented by ().  Interpolating it in a
       list has no effect.  Thus ((),(),()) is equivalent to ().
       Similarly, interpolating an array with no elements is the
       same as if no array had been interpolated at that point.

       A list value may also be subscripted like a normal array.
       You must put the list in parentheses to avoid ambiguity.
       Examples:

           #### SSSSttttaaaatttt rrrreeeettttuuuurrrrnnnnssss lllliiiisssstttt vvvvaaaalllluuuueeee....
           $$$$ttttiiiimmmmeeee ==== ((((ssssttttaaaatttt(((($$$$ffffiiiilllleeee))))))))[[[[8888]]]];;;;

           #### SSSSYYYYNNNNTTTTAAAAXXXX EEEERRRRRRRROOOORRRR HHHHEEEERRRREEEE....
           $$$$ttttiiiimmmmeeee ==== ssssttttaaaatttt(((($$$$ffffiiiilllleeee))))[[[[8888]]]];;;;  #### OOOOOOOOPPPPSSSS,,,, FFFFOOOORRRRGGGGOOOOTTTT PPPPAAAARRRREEEENNNNSSSS

           #### FFFFiiiinnnndddd aaaa hhhheeeexxxx ddddiiiiggggiiiitttt....
           $$$$hhhheeeexxxxddddiiiiggggiiiitttt ==== ((((''''aaaa'''',,,,''''bbbb'''',,,,''''cccc'''',,,,''''dddd'''',,,,''''eeee'''',,,,''''ffff''''))))[[[[$$$$ddddiiiiggggiiiitttt----11110000]]]];;;;

           #### AAAA """"rrrreeeevvvveeeerrrrsssseeee ccccoooommmmmmmmaaaa ooooppppeeeerrrraaaattttoooorrrr""""....
           rrrreeeettttuuuurrrrnnnn ((((ppppoooopppp((((@@@@ffffoooooooo)))),,,,ppppoooopppp((((@@@@ffffoooooooo))))))))[[[[0000]]]];;;;

       Lists may be assigned to if and only if each element of
       the list is legal to assign to:

           (((($$$$aaaa,,,, $$$$bbbb,,,, $$$$cccc)))) ==== ((((1111,,,, 2222,,,, 3333))));;;;

           (((($$$$mmmmaaaapppp{{{{''''rrrreeeedddd''''}}}},,,, $$$$mmmmaaaapppp{{{{''''bbbblllluuuueeee''''}}}},,,, $$$$mmmmaaaapppp{{{{''''ggggrrrreeeeeeeennnn''''}}}})))) ==== ((((0000xxxx00000000ffff,,,, 0000xxxx0000ffff0000,,,, 0000xxxxffff00000000))));;;;

       Array assignment in a scalar context returns the number of
       elements produced by the expression on the right side of
       the assignment:





30/Jan/96                perl 5.002 with                        9





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


           $$$$xxxx ==== (((((((($$$$ffffoooooooo,,,,$$$$bbbbaaaarrrr)))) ==== ((((3333,,,,2222,,,,1111))))))));;;;       #### sssseeeetttt $$$$xxxx ttttoooo 3333,,,, nnnnooootttt 2222
           $$$$xxxx ==== (((((((($$$$ffffoooooooo,,,,$$$$bbbbaaaarrrr)))) ==== ffff(((())))))));;;;           #### sssseeeetttt $$$$xxxx ttttoooo ffff(((())))''''ssss rrrreeeettttuuuurrrrnnnn ccccoooouuuunnnntttt

       This is very handy when you want to do a list assignment
       in a Boolean context, since most list functions return a
       null list when finished, which when assigned produces a 0,
       which is interpreted as FALSE.

       The final element may be an array or a hash:

           (((($$$$aaaa,,,, $$$$bbbb,,,, @@@@rrrreeeesssstttt)))) ==== sssspppplllliiiitttt;;;;
           llllooooccccaaaallll(((($$$$aaaa,,,, $$$$bbbb,,,, %%%%rrrreeeesssstttt)))) ==== @@@@____;;;;

       You can actually put an array or hash anywhere in the
       list, but the first one in the list will soak up all the
       values, and anything after it will get a null value.  This
       may be useful in a _l_o_c_a_l_(_) or _m_y_(_).

       A hash literal contains pairs of values to be interpreted
       as a key and a value:

           #### ssssaaaammmmeeee aaaassss mmmmaaaapppp aaaassssssssiiiiggggnnnnmmmmeeeennnntttt aaaabbbboooovvvveeee
           %%%%mmmmaaaapppp ==== ((((''''rrrreeeedddd'''',,,,0000xxxx00000000ffff,,,,''''bbbblllluuuueeee'''',,,,0000xxxx0000ffff0000,,,,''''ggggrrrreeeeeeeennnn'''',,,,0000xxxxffff00000000))));;;;

       While literal lists and named arrays are usually
       interchangeable, that's not the case for hashes.  Just
       because you can subscript a list value like a normal array
       does not mean that you can subscript a list value as a
       hash.  Likewise, hashes included as parts of other lists
       (including parameters lists and return lists from
       functions) always flatten out into key/value pairs.
       That's why it's good to use references sometimes.

       It is often more readable to use the ====>>>> operator between
       key/value pairs.  The ====>>>> operator is mostly just a more
       visually distinctive synonym for a comma, but it also
       quotes its left-hand operand, which makes it nice for
       initializing hashes:

           %%%%mmmmaaaapppp ==== ((((
                        rrrreeeedddd   ====>>>> 0000xxxx00000000ffff,,,,
                        bbbblllluuuueeee  ====>>>> 0000xxxx0000ffff0000,,,,
                        ggggrrrreeeeeeeennnn ====>>>> 0000xxxxffff00000000,,,,
          ))));;;;

       or for initializing hash references to be used as records:

           $$$$rrrreeeecccc ==== {{{{
                       wwwwiiiittttcccchhhh ====>>>> ''''MMMMaaaabbbblllleeee tttthhhheeee MMMMeeeerrrrcccciiiilllleeeessssssss'''',,,,
                       ccccaaaatttt   ====>>>> ''''FFFFlllluuuuffffffffyyyy tttthhhheeee FFFFeeeerrrroooocccciiiioooouuuussss'''',,,,
                       ddddaaaatttteeee  ====>>>> ''''11110000////33331111////1111777777776666'''',,,,
           }}}};;;;

       or for using call-by-named-parameter to complicated



30/Jan/96                perl 5.002 with                       10





PERLDATA(1)    User Contributed Perl Documentation    PERLDATA(1)


       functions:

          $$$$ffffiiiieeeelllldddd ==== $$$$qqqquuuueeeerrrryyyy---->>>>rrrraaaaddddiiiioooo____ggggrrrroooouuuupppp((((
                      nnnnaaaammmmeeee      ====>>>> ''''ggggrrrroooouuuupppp____nnnnaaaammmmeeee'''',,,,
                      vvvvaaaalllluuuueeeessss    ====>>>> [[[[''''eeeeeeeennnniiiieeee'''',,,,''''mmmmeeeeeeeennnniiiieeee'''',,,,''''mmmmiiiinnnniiiieeee'''']]]],,,,
                      ddddeeeeffffaaaauuuulllltttt   ====>>>> ''''mmmmeeeeeeeennnniiiieeee'''',,,,
                      lllliiiinnnneeeebbbbrrrreeeeaaaakkkk ====>>>> ''''ttttrrrruuuueeee'''',,,,
                      llllaaaabbbbeeeellllssss    ====>>>> \\\\%%%%llllaaaabbbbeeeellllssss
          ))));;;;

       Note that just because a hash is initialized in that order
       doesn't mean that it comes out in that order.  See the
       ssssoooorrrrtttt entry in the _p_e_r_l_f_u_n_c manpage for examples of how to
       arrange for an output ordering.

       TTTTyyyyppppeeeegggglllloooobbbbssss aaaannnndddd FFFFiiiilllleeeeHHHHaaaannnnddddlllleeeessss

       Perl uses an internal type called a _t_y_p_e_g_l_o_b to hold an
       entire symbol table entry.  The type prefix of a typeglob
       is a ****, because it represents all types.  This used to be
       the preferred way to pass arrays and hashes by reference
       into a function, but now that we have real references,
       this is seldom needed.

       One place where you still use typeglobs (or references
       thereto) is for passing or storing filehandles.  If you
       want to save away a filehandle, do it this way:

           $$$$ffffhhhh ==== ****SSSSTTTTDDDDOOOOUUUUTTTT;;;;

       or perhaps as a real reference, like this:

           $$$$ffffhhhh ==== \\\\****SSSSTTTTDDDDOOOOUUUUTTTT;;;;

       This is also the way to create a local filehandle.  For
       example:

           ssssuuuubbbb nnnneeeewwwwooooppppeeeennnn {{{{
               mmmmyyyy $$$$ppppaaaatttthhhh ==== sssshhhhiiiifffftttt;;;;
               llllooooccccaaaallll ****FFFFHHHH;;;;  #### nnnnooootttt mmmmyyyy!!!!
               ooooppppeeeennnn ((((FFFFHHHH,,,, $$$$ppppaaaatttthhhh)))) |||||||| rrrreeeettttuuuurrrrnnnn uuuunnnnddddeeeeffff;;;;
               rrrreeeettttuuuurrrrnnnn \\\\****FFFFHHHH;;;;
           }}}}
           $$$$ffffhhhh ==== nnnneeeewwwwooooppppeeeennnn((((''''////eeeettttcccc////ppppaaaasssssssswwwwdddd''''))));;;;

       See the _p_e_r_l_r_e_f manpage, the _p_e_r_l_s_u_b manpage, and the
       section on _S_y_m_b_o_l_s _T_a_b_l_e_s in the _p_e_r_l_m_o_d manpage for more
       discussion on typeglobs.  See the ooooppppeeeennnn entry in the
       _p_e_r_l_f_u_n_c manpage for other ways of generating filehandles.








30/Jan/96                perl 5.002 with                       11