I believe that %config goes out of scope at the end of the BEGIN block. When the BEGIN block completes, DEMOLISH is able to be called, because %config has just gone out of scope. Now, whenever you are using %config in the rest of your application, I am not certain where the data is coming from.

If you move my %config outside of the BEGIN block, and then change the read_config line to read_config "main.conf" => %config, it should take care if the problems, and you will actually have the data from your configuration file used by the application.

This would have been told you if you had done a use strict; use warnings; before the BEGIN block.

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

In reply to Re: Config::Std to lexial in BEGIN { } throws warning? by MidLifeXis
in thread Config::Std to lexical in BEGIN { } throws warning? by gorash

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.