I don't see any immediate error in your code, but here's a couple of things to think about. First, check the status of your open. If you failed to open the file, printing to the file will silently fail.

sub setDestFile {
  my($self, $file) = @_;
  local(*F);
  open( F, ">$file") or die "Cannot open $file for writing: $!";
  $fh = \*F;
  $self->{'destfile'} = $fh;
}
[download]

Next, munge your contructor to print a header right away. If the open is successful and you don't print a header (you can add an a die to print, also), then you know where to look for the problem.

Lastly, in &output, print $text somewhere where you can see it (STDOUT or STDERR come to mind) in order to verify that you are actually passing something.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.