I wouldn't use import_names. If you find it handy then you are probably also not using strict and that is asking for trouble. Really, I think this is a serious, Don't Do That.

Just use a hash to store names, don't put them into a package. Hashes are easy to clear.

But answering your question, should you be doing something so silly, try the following:

*TEST:: = do {local *NEWGLOB};
But really, I suggest that you don't use that unless you can find from the online documentation (think perldoc) where that information is stored. And there is not a person that I know knows enough to tell you why that code works who would not also agree with my advice to use strict and use hashes. (I am not saying that such people don't exist, but I cannot identify any.)

In reply to Re (tilly) 1: Clearing a namespace by tilly
in thread Clearing a namespace by markguy

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.