I am very worried about the purpose-specific e-mail reader I am writing. Its objective is to download e-mail messages with large PDF/ZIP file attachments, crack out the attachments into files, and pass the work to a pile of website builder code. Some of these PDF/ZIP attachments can be pushing 4 MB.
The e-mail reader program would best be designed to loop through the inbox until all e-mail message have been processed. This means that as soon as one 8 MB MIME e-mail message is finished, the program might start working on another one. Since the Email::MIME library is OO, it sure would be nice to DESTROY the objects from message 1 before beginning message 2.
The notion is ...
if( blah blah blah ) { my $email_text = join( '', $POPobject->get ); $MIMEobject = Email::MIME->new( $email_text ); };
If the coding style looks like FORTRAN, you caught me!
After all the MIME action is done for message 1 (when it's time for the wash-rinse-repeat cycle), I would like to send the multi-megabyte MIMEobject back to the free-space pool with:
$MIMEobject->DESTROY;
... but ... Although perltoot - Tom's object-oriented tutorial for perl describes DESTROY, it strongly hints that civilized programmers newer use it.
Can I be a barbarian in this case? Should I?
Fretting in Texas
In reply to Can I use the OO DESTROY method ... for a good cause by ralphoweber
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |