Your bit of code works exactly as I would like mine to. =( I've put it into an executable and it does what I expect. However, if I gut the function in the original cgi script and put your code in, it fails. In fact, nothing is printed after the eval statement.

I have found, however, that if I substitute &lt; for < in the file and then s/\&lt;/\</g; after it is pulled out, the text will then take the form that I want. Now, though as I stated above, I find that the real failure is in the eval portion. But, I cannot pull out the reason using $@. I think that it fails, but it will not say why.

I am not using Template::Toolkit or the like because I don't know what is going to be on a particular server. I am usually writing code for people who are paying to be hosted on someone's server and I cannot always be sure what is and is not installed there. Likewise, I don't have access to SSH their sites. So, I try to keep it as "pure" as possible. Of course, as anyone will correctly point out, this means that I have to wade through my own errors before the code becomes fit for consumption.

I must be doing something incredibly stupid. But, I can't see it.