in reply to Re: Suggestions for design of a config/rules file
in thread Suggestions for design of a config/rules file

I think the author of the OP can avoid having to use eval. Take a look at Coruscate's response to using require as c like #include?.

Plankton: 1% Evil, 99% Hot Gas.
  • Comment on Re^2: Suggestions for design of a config/rules file

Replies are listed 'Best First'.
Re^3: Suggestions for design of a config/rules file
by halley (Prior) on Jun 09, 2004 at 18:11 UTC
    By eval, I mean any of the class of Perl routines which ultimately do an eval anyway. Both require FILE and do FILE ultimately do an evaluation of the file contents. The rest is syntactic sugar.

    --
    [ e d @ h a l l e y . c c ]