Return-Path: Delivered-To: apmail-perl-dev-archive@www.apache.org Received: (qmail 12454 invoked from network); 24 Nov 2009 16:59:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Nov 2009 16:59:51 -0000 Received: (qmail 39401 invoked by uid 500); 24 Nov 2009 16:59:51 -0000 Delivered-To: apmail-perl-dev-archive@perl.apache.org Received: (qmail 39375 invoked by uid 500); 24 Nov 2009 16:59:50 -0000 Mailing-List: contact dev-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@perl.apache.org Delivered-To: moderator for dev@perl.apache.org Received: (qmail 53593 invoked by uid 99); 24 Nov 2009 04:02:39 -0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of dorian.taylor.lists@gmail.com designates 209.85.222.202 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=x6vZASPeVQcNUV4YrtjG5Kw4LLvAtQhzIv9sYuf3SPA=; b=breL/M2tcHSAqtpurXXYsHGQgCGHhX/8hyj9ghy62Rr+BLJxg5QDHbRKWUZRjEOVD9 7V0+XF8CfX3oI1ALqeZz2mD4ANSB9sEr7hCmNExl58Ao2RKSUALbNZ9HTfT9VCt44CC9 MW6B7iRk4dzJJpD2lDGOaUKzctI5ofey3ndiM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=TQA3EGu3FZZS9hqHbfxT8Y847ntIeU55AmB8RgWdByZqxQGrA9S3pkp0hj+quVzErs uMiohu20DxCD8k6yExkXePvw7cOxVeFz8KN7aXFEKPknfEypo+txVxzWci8GAeqJvkzC aoAalgwgsGJ/c25c2wzSo7ciapfUYsy95SxIs= MIME-Version: 1.0 Date: Mon, 23 Nov 2009 20:02:16 -0800 Message-ID: Subject: Apache2::Reload and fatal warnings From: dorian taylor To: dev@perl.apache.org Content-Type: text/plain; charset=UTF-8 Hey guys, been a while. Was wondering about the behaviour of Apache2::Reload in modules that use warnings FATAL => 'all'; it croaks with a Subroutine foo redefined error which of course is remedied by no warnings 'redefine' in the offending module. Is there a way to incorporate that into Apache2::Reload itself or is the scope too narrow? Regards, -- Dorian Taylor http://doriantaylor.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org For additional commands, e-mail: dev-help@perl.apache.org