Re^3: repeated use of module and EXPORT

How about having a third package, let's call it util, that contains the shared code. Include util in both libs and dbg, and you no longer have the loop.

--MidLifeXis

Comment on Re^3: repeated use of module and EXPORT

Replies are listed 'Best First'.
Re^4: repeated use of module and EXPORT by shmem (Chancellor) on May 23, 2008 at 19:35 UTC
... and you no longer have the loop. There is no loop. Each piece of code gets compiled once. As one piece of code uses the other one, it gets what is defined at that moment of compilation, that's all - perl won't loop switching compilation from one to the other and from the other to the one and back and forth again over and over. --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]
Re^5: repeated use of module and EXPORT by MidLifeXis (Monsignor) on May 24, 2008 at 03:07 UTC
I wasn't implying that there was a execution loop. More a logical design loop. Sorry for the poor conveyance of meaning :) --MidLifeXis	[reply]
Re^4: repeated use of module and EXPORT by rpelak (Sexton) on May 23, 2008 at 18:52 UTC
My reply to this doesn't seem to be showing up, but I will try one last time... That doesn't work out. In the real case the Z module is a dbg module, and all modules use dbg... so the new module would also use dbg, and the loop would still be present.	[reply]