Re^4: Recover a path from a config file

From what I can see from your config file, you are using a "BAD idea". In general, I would not use executable Perl code for a simple configuration file because there are standard formats for this, see INI file. There are number of Perl modules that can parse an .INI text file. I would use one of those! I don't see anything that would prevent that?

Comment on Re^4: Recover a path from a config file

Replies are listed 'Best First'.
Re^5: Recover a path from a config file by Chaoui05 (Scribe) on Jun 07, 2016 at 08:10 UTC
Yes Marshall , i thought about it. But in my case, to improve my level in Perl , i have to use as often as possible, executable Perl. Of course, some modules can do it well. ***Lost in translationTIMTOWTOI**	[reply]
Re^6: Recover a path from a config file by Marshall (Canon) on Jun 09, 2016 at 02:14 UTC
I use this kind of config.file in order to improve my Perl approach. If you want to improve your Perl approach, I would recommend using the right technique for the right job. Yes, your config file can be "made to work". But, you have created something that only you can modify or use. I would not expect any of my users to modify this file - there are a lot of arcane syntax issues with it because it is really a Perl program. I see that as a disadvantage. In general for my INI type config files, I strive for a comprehensible format that a non-Perl person can modify and understand. I document all the stuff that a user might want to modify or understand. Sometimes I put in say a DEBUG section and withhold some features to keep the users out of trouble. When a weird problem develops, I can explain clearly with simple instructions what to do in order to generate a bug report that I can understand. Or perhaps I put in something like `DUMP_DECISION_STACK =0` and can tell the user to set that =1. I often use the INI file during development as debug "level" tool.	[reply] [d/l]