in reply to Re: Namespace after forking()+eval()ing providing unexpected results
in thread Namespace after forking()+eval()ing providing unexpected results

That makes lots of sense. I couldn't understand why if the fork/eval was out in LaunchMod.pm it wouldn't work, yet it would in Launcher itself - I saw only that it was doing the same code in two different places, the 'package' declaration didn't hit me...
The 'package main;' makes the code work as I want it to, so I'm quite happy.

The code example given is, as you can imagine, greatly simplified from the original software - where I'm using a number of globals to relate back and forth between Code and CodeMod.pm, as there are a lot of routines that use these globals - and I began to feel that passing three vars to one sub, which then distributes that to a bunch more, collects the results... and passes it all back? It just started getting really ugly...

My thanks Chipmunk,
JP
-- Alexander Widdlemouse undid his bellybutton and his bum dropped off --

  • Comment on Re: Re: Namespace after forking()+eval()ing providing unexpected results