Since you seem to be on a *n*x machine, seems like this would be a lot simpler (assuming a bash shell): 
$ find /tmp/rja/find_test -type f -print0 |
  perl -0 -ne 'chomp;
  $t=do{local $/; open(T,"<",$_);<T>};
  print "$_ is completely CRLF\n" unless ( $t =~ /(?<!\r)\n/ )'

[download]

But then, I've never been a fan of File::Find, ever. It's just too weird and too slow.

BTW, are you looking for files that are completely CRLF, as I assumed in my snippet, or rather for files that have any CRLF in them? If the latter, the last part of the snippet would be  if ( $t =~ /\r\n/ ) update: and I'd change "is completely" to "has".

In reply to Re: grep and find file weirdness by graff
in thread grep and find file weirdness by reasonablekeith

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.