Sorry, I mistyped the destination address -
Hi. This is the qmail-send program at tmtowtdi.perl.org. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <[EMAIL PROTECTED]>: Sorry, no mailbox here by that name. (#5.1.1) --- Below this line is a copy of the message. Return-Path: <[EMAIL PROTECTED]> Received: (qmail 13563 invoked from network); 6 Aug 2000 19:36:07 -0000 Received: from c878404-a.pinol1.sfba.home.com ([EMAIL PROTECTED]) by tmtowtdi.perl.org with SMTP; 6 Aug 2000 19:36:07 -0000 Received: from InfoCorps.Net (IDENT:[EMAIL PROTECTED] [24.10.176.98]) by c878404-a.pinol1.sfba.home.com (8.9.3/8.9.3) with ESMTP id MAA24221 for <[EMAIL PROTECTED]>; Sun, 6 Aug 2000 12:37:14 -0700 Sender: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Date: Sun, 06 Aug 2000 12:37:14 -0700 From: "Robert B. Andrews" <[EMAIL PROTECTED]> X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.2.14 i686) X-Accept-Language: en MIME-Version: 1.0 To: [EMAIL PROTECTED] Subject: Author Registration Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, I have a module to contribute, but am not a registered author. My email address: same as on the header for this mail My preferred user id on CPAN: rbandrews Module: Name DSLL Description --------- ------- --------------------------------------------------------------------- ErrorC Rdpf Signal Traps/Stack Traces/Memory Leak Checks Description: Handlers for signals plus __WARN__ & __DIE__ provide stack traces for signals not caught elsewhere. Uses Config to determine whether the signals even exist before attempting to handle them. Provides summary to file. Usefull when developing new code involving several cooperating processed running in the background, or using code/modules contributed by others. The stack trace code is similar to that available in Carp, with more information. Routines are available as replacements for warn()/die() or cluck()/confess. Memory leak check code is not loaded or exexuted unless eneabled. This code relies on Devel::Leak. A simple, one line interface allows one to check a subroutine to see if it is causing memory leaks. When enabled, the END() code automatically prints a summary of all tests to a file. Summary information includes the program name, pid, and for each routine tested, the package name, subroutine name, and summary of unreclaimed SV's. Works for multiple programs, and multiple packages/subs simulteneously. I personally used it with 20 simultaneous web grabbers to verify that the libwww code was not leaking. I have personally tested and used this code extensively, but that's it.
