in reply to Re^2: Inline::Files unopened filehandle errors redux
in thread Inline::Files unopened filehandle errors redux

but when I try to re-open the virtual file I get: Variable "$CONFIG" is not imported

Yes. That's what I get with 5.10 also. It never used to happen. From mmeory, it worked correctly circa 5.8.1|2£|4|5'ish. But my memory is fallible and I don't have the capacity to test that aassertion.

I tried adding our $CONFIG; at the top of the file and that changes the problem to: 

Use of uninitialized value $CONFIG in concatenation (.) or string

[download]

But doesn't fix it entirley.

Like I said, I think that it suffers from a lack of ongoing maintenance. As with s many of theDamian's modules.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP PCW It is as I've been saying!(Audio until 20090817)

Replies are listed 'Best First'.
Re^4: Inline::Files unopened filehandle errors redux
by Anonymous Monk on Oct 17, 2009 at 00:10 UTC
    I think that it suffers from a lack of ongoing maintenance. As with s many of theDamian's modules.

    That may be generally true, but in this case the maintainer isn't Damian, it's Alberto Simões. Who most recently released an update in May this year. And who can't really be blamed for this problem either, since no bug report has been filed on this issue.

[reply]

      I mean no discourtesy to TheDamian. Many of his modules have been handed off to others, whilst many others are deemed unsupportable.

      And without in any way in inpuning any particular current maintainer, including Alberto, TheDamian is a hard act to follow. Especially TheDamian of the era when he wrote most of his most sophisticated modules. I have my doubts, even if he was still active in the P5 arena, whether he would be able to maintain the depth and breadth of knowledge it took to make many of these modules work in the first place, in the light of the ceaselessly moving target of both the state of the internals and the multiple hands on the tiller pulling it in ever new directions. As trends and fads change, so the ability of even the most talented individuals to keep up is limited, especially as the demands and rhythms of real life take hold.

      It's also an extraordinarily thankless task to maintain the works of an extraordinary author. Like asking a session musician to maintain the works of Beethoven; or a house painter to touch up a Cezanne.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]
        You're quite right, on all counts.

        Interestingly, in Perl Best Practices, Damian quotes a very relevant aphorism from Brian Kernighan: "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it."

        Advice we should all live by. :-)

[reply]
[d/l]

In Section Seekers of Perl Wisdom