perl-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: saving the 'here is how to report bugs' cycle
Date Wed, 05 Nov 2003 09:56:51 GMT
Geoffrey Young wrote:
> 
>> Here it is. Now each project using Apache::Test can easily supply its 
>> own function to be executed on 't/TEST' failure. In the case of 
>> mod_perl we just print:
>>
>> +--------------------------------------------------------+
>> | Please file a bug report: http://perl.apache.org/bugs/ |
>> +--------------------------------------------------------+
> 
> 
> nice!
> 
>> +sub try_bug_report {
>> +    my $self = shift;
>> +    if ($? && $self->{opts}->{bugreport}) {
>> +        $self->bug_report if $self->can('bug_report');
>> +    }
>>  }
> 
> 
> given the way it's implemented in t/TEST.PL, you should only need
> 
> sub bug_report {}
> 
> the subclassing should take care of the rest.

Certainly. Thanks for the idea!

> I like this.  I like it a lot :)

I like it too ;)

I've found at least one problem and fixed it. I've committed a different 
version with much less intrusive changes, keeping t/TEST autogenerated.

__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org


Mime
View raw message