An array might be mixed, containing both objects and strings (or other scalar values). Also, some might be references to unblessed data structures.

If the strings you want to construct from objects can be obtained by overloading double-quotes, then you don't need to test; just say, 

sub foo {
    my @stringy_args = map { "$_" } @{shift()};
    # . . .
}

[download]
If overloading quotes is not feasable, you can say, 
sub foo {
    my @stringy_args = map { ref ? bestring($_) : "$_" } @{shift()};
    # . . .
}

[download]
That lumps blessed objects with other references, and numbers with strings. For finer discrimination, Scalar::Util has a bunch of functions like blessed and looks_like_number to help out.

After Compline,
Zaxo

In reply to Re: Distinguishing between an array of objects and an array of strings by Zaxo
in thread Distinguishing between an array of objects and an array of strings by loris

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.