Your code looks fine. The slashes will not interfere with forming hash keys.

The problem appears to be that the trailing data is making each element of @array unique. If there is no way of distinguishing where a path ends and data starts, you have an intractable problem. Ideally, the data should start with ASCII NUL, which cannot be part of a file name. Then, 

my %saw;
@out = grep {!$saw{$_}++}
       map  {substr $_, 0, index($_,"\0")}
       @array;

[download]
If you don't have that luxury, can you characterize what the filename extensions are? Matching those can locate the end of the path for you.

After Compline,
Zaxo

In reply to Re: grep confusion by Zaxo
in thread grep confusion by Baratski

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.