Re^5: Config::Std to lexial in BEGIN { } throws warning?

Three different posts, at least two slightly different questions (with different solutions).

Could you please post code, that when run, actually exhibits the full and complete problem that you are seeing. Also, please attach the actual error / warning message that is generated. An actual, fully working demo that reproduces the problem will help greatly.

Input data (a configuration file), output data (the warnings or errors thrown), code that generates the output data from the input data, and what you actually expect the output data to look like would be most helpful.

Or, you can keep spoon feeding us information until we accidentally hit upon a solution (or something that looks like a solution).

Perhaps I am just foggy in the head today.

It is said that "only perl can parse Perl." I don't even come close until my 3rd cup of coffee. --MidLifeXis

Comment on Re^5: Config::Std to lexial in BEGIN { } throws warning?

Replies are listed 'Best First'.
Re^6: Config::Std to lexial in BEGIN { } throws warning? by gorash (Novice) on Feb 23, 2010 at 18:52 UTC
My apologies, if I didn't get my point across. I did not want a solution for my program, which is why I intentionally posted a minimal proof of concept. The original snippet is working and demonstrates what problem I have, that reading a config file, which is no problem normally, generates a warning when forced to execute in `BEGIN`. Input data (apart from a file that is recognized as a config file by Config::Std), output data does not exist. Also I do not want to fix anything, I want to understand why a 'once' warning is triggered in this special case, where in my intuition it should not be triggered.	[reply] [d/l]

Replies are listed 'Best First'.

Re^6: Config::Std to lexial in BEGIN { } throws warning?
by gorash (Novice) on Feb 23, 2010 at 18:52 UTC

My apologies, if I didn't get my point across. I did not want a solution for my program, which is why I intentionally posted a minimal proof of concept.

The original snippet is working and demonstrates what problem I have, that reading a config file, which is no problem normally, generates a warning when forced to execute in BEGIN. Input data (apart from a file that is recognized as a config file by Config::Std), output data does not exist.

Also I do not want to fix anything, I want to understand why a 'once' warning is triggered in this special case, where in my intuition it should not be triggered.

[reply]
[d/l]