Although $^O is the literal answer to your question the answer for portability is to use perls internal functions only rather than system calls. That way the port of Perl takes care of the port of you script for you. This could be a lot more terse if desired: 

use Cwd;

opendir my $dir, cwd() or die "Can't read ".cwd().": $!\n";
my @contents = readdir $dir;
closedir $dir;

my @dirs = grep{ -d and $_ ne '.' and $_ ne '..' } @contents;
print "DIR $_\n" for @dirs;

#my @files= grep{ -f } @contents;
#print "FILE $_\n" for @files;

[download]

In reply to Re: recognizing OS by Anonymous Monk
in thread recognizing OS by PerlZealot

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.