in reply to Re^4: 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.

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

  • Comment on Re^5: Looking for some insight on Tie::File

Replies are listed 'Best First'.
Re^6: Looking for some insight on Tie::File
by stevieb (Canon) on Jan 09, 2016 at 01:42 UTC

    I apologize. I most definitely stand corrected.

      I apologize. I most definitely stand corrected.

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

        it's all good. Sometimes we (I) get over-enthused and need to be reminded that learning is why I'm here. Speaking for myself, the odd kick here and there is what ensures that I stay on top of the game as best I can, and I don't ever quit questioning.

        Kudos. I really do appreciate the new avenue I have to research, as much as I do your respectful demeanor throughout this thread.