At 5:16 PM +0000 4/3/00, Dermot Musgrove wrote:
>[EMAIL PROTECTED] wrote:
>>
>>  This distribution has been tested as part of the cpan-testers
>>  effort to test as many new uploads to CPAN as possible.  See
>>  http://testers.cpan.org/
>>
>>  Please cc any replies to [EMAIL PROTECTED] to keep other
>>  test volunteers informed and to prevent any duplicate effort.
>>
>>  --
>>  All tests passed.  There were lots of warnings:
>Hi,
>
>firstly, thanks for testing my module. It is especially interesting to see
>it tested on perl 5.006.
>
>Most of the warnings were diagnostic messages generated by Glade-Perl and
>are expected output of the test (verbose = 2).
>
>However, I don't yet have version 5.006 of perl so I would be grateful for
>any advice on the following warnings.
>
>[...]
>>  (in cleanup) Can't access method `DESTROY' in class Glade::PerlSource
>>  We were called from Glade::PerlGenerate, /Glade/PerlGenerate.pm, 86
>[...]
>>  (in cleanup) Can't access method `DESTROY' in class Glade::PerlProject
>>  We were called from main, test.pl, 0
>
>Should I write a sub DESTROY and what should it do?

According to the docs (I'm looking at 5.6's perltoot), DESTROY does 
any cleaning up you need to do on exit.  An empty one is probably 
fine unless you actually want to use it for something.

It's probably showing up because of this change:

        Failures in DESTROY()

        When code in a destructor threw an exception, it went
        unnoticed in earlier versions of Perl, unless someone hap-
        pened to be looking in $@ just after the point the
        destructor happened to run.  Such failures are now visible
        as warnings when warnings are enabled.


>
>I'm sorry to ask baby questions like this but it is the first time that I
>have heard of this warning and I would appreciate a URL of a FM to R - if
>you have one handy :)


I've looked around a little and don't see the docs anywhere on line 
yet.  AFAIK, the only way to get the docs is out of the distribution 
tarball.

>
>Thanks again, Dermot

-- 
--
Paul Schinder
[EMAIL PROTECTED]

Reply via email to