The problem is the syntax (see perlintro). Its like writing 
$ perl -le " print foo bar "
Can't locate object method "foo" via package "bar" (perhaps you forgot
+ to load "bar"?) at -e line 1.

$ perl -e "warn foo bar "
Can't locate object method "foo" via package "bar" (perhaps you forgot
+ to load "bar"?) at -e line 1.

$ perl -e "warn bar->foo "
Can't locate object method "foo" via package "bar" (perhaps you forgot
+ to load "bar"?) at -e line 1.

[download]

arguments to functions need to be seperated by commas, and strings should generally be quoted

If you had quoted them 

$ perl -e "warn 'foo' 'bar' "
String found where operator expected at -e line 1, near "'foo' 'bar'"
        (Missing operator before  'bar'?)
syntax error at -e line 1, near "'foo' 'bar'"
Execution of -e aborted due to compilation errors.

$ perl -Mdiagnostics -e "warn 'foo' 'bar' "
String found where operator expected at -e line 1, near "'foo' 'bar'" 
+(#1)
    (S syntax) The Perl lexer knows whether to expect a term or an ope
+rator.
    If it sees what it knows to be a term when it was expecting to see
+ an
    operator, it gives you this warning.  Usually it indicates that an
    operator or delimiter was omitted, such as a semicolon.

        (Missing operator before  'bar'?)
syntax error at -e line 1, near "'foo' 'bar'"
Execution of -e aborted due to compilation errors (#2)
    (F) Probably means you had a syntax error.  Common reasons include
+:

        A keyword is misspelled.
        A semicolon is missing.
        A comma is missing.
        An opening or closing parenthesis is missing.
        An opening or closing brace is missing.
        A closing quote is missing.

    Often there will be another error message associated with the synt
+ax
    error giving more information.  (Sometimes it helps to turn on -w.
+)
    The error message itself often tells you where it was in the line 
+when
    it decided to give up.  Sometimes the actual error is several toke
+ns
    before this, because Perl is good at understanding random input.
    Occasionally the line number may be misleading, and once in a blue
+ moon
    the only way to figure out what's triggering the error is to call
    perl -c repeatedly, chopping away half the program each time to se
+e
    if the error went away.  Sort of the cybernetic version of 20 ques
+tions.

Uncaught exception from user code:
        syntax error at -e line 1, near "'foo' 'bar'"
        Execution of -e aborted due to compilation errors.

[download]
And it says A comma is missing.

In reply to Re^3: install multiple modules at once using CPAN by Anonymous Monk
in thread install multiple modules at once using CPAN by ruqui

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.