use Perl

• Interface (Score:2, Informative)

  by PerfDave (3311)

  Yeah, I thought about doing a "nice" version of File::Find myself. I wanted to tie in a few things as well - the ability to get structured data as well as lists from it, and to cache data.

  I'm not sure I like the stream-y interface you've got here - powerful, but violates the KISS principle which makes File::Find such a pain in the arse to use at the moment. I'd pictured more of a hash-based interface, but I hadn't thought of options so much (but I guess they could be done either by regexps or arrays).

  my
  • Re:Interface (Score:1)

    by Thomas (520) on 2002.07.19 10:10 (#10858) Homepage Journal

    It was almost the same thing I came up when thinking about it.
    
    I'd like to see something like this:
    
    my @files = find('/tmp', { maxdepth => 10, mindepth => 5, name => qr/\.*\.c$/ });
    
    (Which I btw already have working in a small example I hacked together.) I really like your idea of using arrays for alternation, but how do you decide wheter to AND or OR? (AND doesn't make much sense in your example though).
    
    Instead of returning the files I'd also consider an 'exec' like option that took a sub ref or function and just passed the filename to it as the first argument.
    
    That is about all I'd need from a Perl find.

    Reply to This

    Parent

    • Re:Interface (Score:1)

      by Thomas (520)

      I've made a quick implementation of what I'd like to see File::Find offer instead. I think it might be a good idea to do a real print function and instead call the one I've used 'return'.
      
      It is of course not nearly done, but if anyone feel they like the concept and want to use it please feel free to do so.
      
      package Find;
      
      use strict;
      use vars qw($VERSION @EXPORT @EXPORT_OK %EXPORT_TAGS @ISA);
      require Exporter;
      
      @ISA = qw(Exporter);
      @EXPORT = qw(find);
      @EXPORT_OK = qw(find);
      
      $VERSION = '0.1';
      
      sub find {
       
    • Re:Interface (Score:1)

      by richardc (1662)

      my @files = find('/tmp', { maxdepth => 10, mindepth => 5, name => qr/\.*\.c$/ });

      Warning: hashes found not to have a predictable order. Evaluating the rules in a known order can have a huge effect on efficiency. Please look at rafael's "Good example for 'or'" comment, if the exec happened first you'd really feel a hit from it just shortcutting that happens at name('*.pl').

      (Which I btw already have working in a small example I hacked together.)

      Please, don't let me stop you releasing your
      • Re:Interface (Score:1)

        by richardc (1662)

        I thunk it out a bit more, and now it's possible to do this:

        # extract from the test suite
        # procedural form of the prune CVS demo
        use File::Find::Ruleset 'find_ruleset';
        $f = find_ruleset(or => [ find_ruleset( directory =>
                                                name      => 'CVS',