My most esteemed monks.

Here's some code:

package FileHandle::A; sub TIEHANDLE { my $self = shift ; my $fh = [ shift ]; bless \$fh => $self; } sub PRINT { my $self = shift; my @list = @_; my $fh = $$self->[0]; print $fh @list; } tie *STDOUT, 'FileHandle::A', *STDOUT; print "testing";

Basically, I was getting a Deep recursion error and I tried minimalizing the error to post here. The code I present here segfaults on my machine.

I think I know why... PRINT calls print which calls PRINT which calls print which calls... you get the idea...

I tried a bunch of things already, including CORE::print() and even passing a special parameter to stop the recursion, which indeeds stops it, but... doesn't print.

I know the example looks weird; it really isn't what I want to do, but it demonstrates my problem. Can anyone point me in a direction that solves it?


In reply to Solving Deep recursion with a tied Filehandle by cog

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.