LanX wrote:
So exporting the whole typeglob will fix it.:).

In case exporter doesn't support * , use your own import

This perfectly does the job!

I replaced 

our @EXPORT = qw( %debug $d_area dsay );

[download]
by 
our @EXPORT = qw( %debug *d_area dsay );

[download]
in Dsay.pm.

I now can use 

sub one {
    local $d_area = "one";
    dsay "debugging output from one";
}

sub two {
    local $d_area = "two";
    dsay "debugging output from two";
}

$debug{TWO} = 1;
one;
two;

[download]
and get debugging output from the 'two' area only. Debugging output stops as soon as the localized $d_area value drops out of scope.
And this without the need of qualifying $Dsay::d_area anymore!

Thank you so much! This really helps, and I have learned a lot!

In reply to Re^2: 'local' for imported variables doesn't work as expected by muthm
in thread 'local' for imported variables doesn't work as expected by muthm

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.