use Perl

• So many to choose from (Score:1)

  by grink (8549)

  The great thing about Config:: is that there are so many to choose from...
  
  I've come to like using Catalyst::Plugin::ConfigLoader as a straightforward way of getting a text config into a hash.
  
  C::P::CL is built on top of the excellent Config::Any, so you can use .ini, .yaml, .conf (Config::General), .json, and even .pl (maybe more?)
  Unfortunately, C::P::CL is built into Catalyst, so I (plug) wrote a factored out version called Config::JFDI
  
  If you're not afraid of a few dependencies, then you should give Config: [cpan.org]
• I tend to agree (Score:2)

  by grantm (164)

  In my experience, YAML is a read-only format. It's probably just that I haven't used it enough but every time I try to hand craft YAML I get bitten by the subtleties.

  I had a brief flirtation with XML and a config file format some years ago and I still paying the price :-)

  I've used hand-rolled parser code for ini-style configs a number of times recently. I haven't bothered with implementing [sections] but often need to include multi-value items. The way I tend to handle that is by putting an '@' prefi
  • Re: (Score:2)

    by TeeJay (2309)

    Sounds like reinventing the wheel to me : Config::Tiny and Config::Simple (look no dependancies (http://cpandeps.cantrell.org.uk/?module=config%3A%3Asimple&perl=any+version&os= any+OS) are both simple, small and deal with most edge cases so you don't have to.
    

    --
    
    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
• My favorite configuration format is (Score:1)

  by btilly (5037)

  Perl! [perlmonks.org]
  • Re: (Score:1)

    by markjugg (792)

    Mine is as well. I like the simplicity and flexibility, and my reality is that the config files are edited by programmers, so the Perl syntax is not "scary".
• Config::Tiny (Score:1)

  by Alias (5735)

  ... is probably marginally better than cutting and pasting that 50 lines.
  
  Or alternatively, cut and past Config::Tiny into your code as Module::Config.
  
  • Re: (Score:2)

    by Matts (1087)

    Yup. The point being that configuration data is pretty simple and you shouldn't over complicate it unless you have really crazy needs.
    • Re: (Score:1)

      by Ron Savage (5224)

      What the point of the *s in:
      s/^\s*//;
      s/\s*$//;
      Surely you never want to match 0 spaces, so why not use s+? (That's an English ?, not a Perl one).
      
      • Re: (Score:1)

        by Alias (5735)

        Hrm... I'm not sure there is a point, could just be a legacy of some old code that did something like
        
        s/^\s*something//;
        
        
      • Re: (Score:2)

        by Matts (1087)

        Just habit. Everywhere I've ever seen whitespace removed it's used \s* rather than \s+. Perhaps historically \s* matched faster?