|laziness, impatience, and hubris|
Re^5: Postpone garbage collection during a child process run?by Anonymous Monk
|on Oct 07, 2010 at 07:14 UTC||Need Help??|
"What you describe is not what happens." So you are calling me a liar?
No, Corion did not call you a liar. He did not even call you mistaken, confused.... what you describe is simply not how perl works, sorry.
"You have a subroutine which triggers some action at a distance, namely, cleaning out a hash." Did I ever say this? No!
Actually, that is exactly what you described, sorry.
A static, read-only hash should not disappear!
Can you show an example (real perl code) that creates a static read-only hash? I'll be happy to show at least two ways it can disappear (no c voodoo, just regular perl code).
Your assumptions are ...Life should be so simple.
Sure, someone with over 10 years experience could make bad assumptions, but we only have your descriptions as source material.
Note: I have tried to ask intelligent, courteous and accommodating questions to this qroup. I don't know what I did to have such an aggressive response, maybe some-one is having a "bad hair day", but please if you don't understand the question, or you can't grasp the complexity of the problem, just don't respond!
Please see http://perl5.git.perl.org/perl.git?a=search&h=blead&st=free&s=Corion. We've all been there, but try to remember the golden rule.