comment on

Thank you for the tips! I actually took the time to install these modules, and try to do the same job with them before answering, so I would know a little what I am talking about.

First off, I want to limit myself to STDOUT, in this case, because I want the impact on the original script to be as small as possible - ie, I'd like it to just be an extra use line that I can insert into each script. But anyways, here is how it all worked out for me:

I could, after some tinkering, accomplish the same thing with Tie::Handle::Scalar, as I do now. I'll just throw up the code right away:

use Tie::Handle::Scalar;
tie *STDOUT, 'Tie::Handle::Scalar';

END
{
    my $output;
    while(<STDOUT>)
    {
        $output .= $_;
    }

    &on_finish(\$output);

    untie *STDOUT;

    print $output;
}

sub on_finish
{
    my $stdout_ref = shift;

    # Insert a stylesheet link last in the head section
    $$stdout_ref =~ s{(</head>)}{<link rel="stylesheet" type="text/css
+" href="/css/style.css" />\n$1}i;
}
[download]

I put this in a module, and used it instead of the original example file - the sub routine is the exact same, so I could compare results.

The above code does work, and comparatively, it uses about one third of the code in my module to do the same thing. But I do have some issues with it - you be the judge if I am just defending my code, or if I have any substance in these "complaints". :)

I don't want to insert this whole chunk into my scripts, CGI or not, even though I *could* have it stored somewhere and just copy/paste it in, and =pod it out I guess. So I'd still wrap it into a wrapper module, which means that it gets the extra overhead of loading this other module (petty, probably) that does a lot I don't need, and that I need this module too, to be installed. It is not a standard module. Neither is mine, but that'd make it two.
It uses a file to read and write from, which could result in some IO going back and forth, and it generally seems if not bad, so overkill for my needs. Of course, if my memory approach causes swapping (don't think so though, really), then it is about the same. On win2k, it also didn't remove the files it created, it did on linux though. The NT family is like that sometimes - it could be a problem though.

Not big things, I guess, but it does a lot I don't need, in probably too general ways, plus I'd want that wrapper anyways. It could have saved me some POD writing though, if I wanted a one-time solution. It would most certainly work.

IO::String and IO::Stringy I am less certain about. I couldn't get either to do this at all. Possibly because I don't understand the terse docs, but I tried most possible combinations of what was there at least. It is possible that it isn't meant to do this exact thing too, and equally possible I am doing it wrong.

Most things still apply though, it would take an extra wrapper to get it where I want, etc.

Well, I guess my petty "defence" is that I wanted something that did something, that something only, and did it good while being easy to use. If I succeeded is another matter entirely.

I did lots of searches for something that could do this, and I *still* missed those modules, that is almost unbelievable. Especially since I searched the Tie::* modules pretty good. Guess I didn't look closely enough at exactly what modules did.

Again, thanks for pointing these out to me. I'd still stick with what I wrote, now that it is written, but I might have reconsidered had I found this. Not that it matters, writing code is what is fun after all. :)

You have moved into a dark place.
It is pitch black. You are likely to be eaten by a grue.

In reply to Re(2): STDOUT::Capture - manipulate STDOUT by Dog and Pony
in thread STDOUT::Capture - manipulate STDOUT by Dog and Pony

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:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.