in reply to Re: File::Find considered hard?
in thread File::Find considered hard?

How often have you written code like the following?
Never.
chomp (my @files = `find .`);
is shorter, immediately clear (at least to me), and works on any platform I would care about.

Abigail

Replies are listed 'Best First'.
Re: Re: File::Find considered hard?
by etcshadow (Priest) on Mar 14, 2004 at 21:29 UTC
    Good to know... now I can be rox0rzing all over your systems by creating a file named /home/etcshadow/foo\n/etc/shadow.

    w00t!

    </script-kiddie>

    ------------ :Wq Not an editor command: Wq
      now I can be rox0rzing all over your systems by creating a file
      No, you won't be able to.

      Abigail

        A fine perpetuation of ignorance.

        Perhaps if you're going to bother to post, you could actually explain why that doesn't cause any problems.

        It's rather sad to see perlmonks dwindle down to nothing more than "do this" / "no that's bad" / "no it's not" / "yes it is."

        I'll be on my way now.

Re^2: File::Find considered hard?
by Anonymous Monk on Mar 15, 2004 at 06:06 UTC
    works on any platform I would care about.

    Hrm. Do other version of Windows other than XP spit out the info you'd expect from 'find .'? Such a command on my WinXP box is invalid.

      Do other version of Windows other than XP spit out the info you'd expect from 'find .'?
      1. Yes, assuming you've installed an appropriate Unix toolset.
      2. I don't care at all about Windows.

      Abigail