in reply to Re^3: Looking for some insight on Tie::File
in thread Looking for some insight on Tie::File

My bad... I'll re-state... "an unbounded, unconfined and completely dangerous assignment to a variable namespace that has global symbolic table access. This clobberes the symtab, which is *always* a bad idea, unless you *really* know what you're doing". No matter how you word it, it's very bad advice.

Update: The people answering questions should *always* ensure their responses work properly without issue under the strict and warnings pragmas, and thereafter, advise the OP to do so as well.

Replies are listed 'Best First'.
Re^5: Looking for some insight on Tie::File
by Anonymous Monk on Jan 09, 2016 at 01:27 UTC

    My bad... I'll re-state... "an unbounded, unconfined and completely dangerous assignment to a variable namespace that has global symbolic table access. This clobberes the symtab, which is *always* a bad idea, unless you *really* know what you're doing". No matter how you word it, it's very bad advice.

    The re-statement is also wrong

    It neither unbounded nor unconfined, its limited to the subs the OP has ... or the file

    It also isn't completely dangerous

    Nor is it "an assignment to a variable namespace that has global symbollic table access"

    It overrides one single symbol exactly, with lexical scoping (ie safe), temporarily

    You're wrong, learn from it

    Update: The people answering questions should *always* ensure their responses work properly without issue under the strict and warnings pragmas, and thereafter, advise the OP to do so as well.

    This guys answer does work under both strict and warnings

    Al so, there is no such requirement for posting on perlmonks

[reply]

      I apologize. I most definitely stand corrected.

[reply]

        I apologize. I most definitely stand corrected.

        thank you:) I felt weird writing that "learn" part

[reply]

In Section Seekers of Perl Wisdom