I assume a new install of PERL 5.8.8 would require all our modules to be reinstalled.

Well ... that's definitely not true wrt Mandrake linux, and it's definitely not true wrt Win32. I doubt very much that it's true wrt Solaris 10, but I don't really know. With my Mandrake linux, all I had to do was install perl 5.8.8, and the relevant 5.8.7 directories were automatically added to @INC, thereby alleviating any need to re-install modules. On Win32, however, that didn't happen. But all that was necessary was to copy the entire 5.8.7/site/lib/ directory to 5.8.8/site/lib/. You could do the same thing on Solaris if necessary.

I also wonder if you need to 'use diagnostics;'. I suspect that if the diagnostics module is not loaded, then the problem will go away.

Cheers,
Rob

In reply to Re: CGI::Carp::warn bug in 5.8.7 Deep recursion? by syphilis
in thread CGI::Carp::warn bug in 5.8.7 Deep recursion? by jbrose

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.