but nothing actually happens until the garbage-collector makes its midnight run

Dave.

> No, perl doesn't use a garbage collector.

most probably a problem of fuzzy terminology¹, perldoc talks about "garbage collection":

 Perl uses a fast and simple, reference-based garbage collection system

see perlobj#Two-Phased-Garbage-Collection

But as opposed to mark-and-sweep Perl's runtime approach is very simple an efficient.

OTOH it can't handle circular references.

And even if mark-and-sweep was used, IIRC Python does it and is still very performant. ²

Cheers Rolf

UPDATES:

¹) from perlglossary

       garbage collection
           A misnamed feature--it should be called, "expecting your mo
+ther to
           pick up after you".  Strictly speaking, Perl doesn’t do thi
+s, but
           it relies on a reference-counting mechanism to keep things 
+tidy.
           However, we rarely speak strictly and will often refer to t
+he
           reference-counting scheme as a form of garbage collection. 
+ (If
           it’s any comfort, when your interpreter exits, a "real" gar
+bage
           collector runs to make sure everything is cleaned up if you
+’ve been
           messy with circular references and such.)
[download]

²) more complicated: "While Python uses the traditional reference counting implementation, it also offers a cycle detector that works to detect reference cycles."

So perhaps I'm right to be concerned about cleanup... the program itself will be installed as a daemon, so anything I can do to prevent long term consumption, or to force garbage collection would be good.

What method do you recommend to remove the array? My read of delete (man page) against an array leads me to believe that I'm still waiting on true garbage collection

> So perhaps I'm right to be concerned about cleanup

No don't worry, Anonymous probably confuses the garbage collection systems.

Perl doesn't freeze!

Just be careful to not produce circular references.

Cheers Rolf