Using FileHandle as recommended in the perlform documentation works for me:

#!/usr/bin/perl -w
use strict;
use warnings;
use FileHandle;

open my $fh, '>', '/tmp/output.txt' or die $!;

my $data = 'This is a test';
format LEFT  =
@<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
$data
.
format RIGHT = 
@>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
$data
.

format_name $fh "LEFT";
write ($fh) or die $!;
format_name $fh "RIGHT";
write ($fh) or die $!;

close ($fh) or die $!;
exit;

[download]
Please note in your answers I'm not a programmer - I'm an engineer who simply uses perl to make my life easier.

The easier you want your life to be, the more you will use perl and therefore the more you will become a programmer.

:-)

In reply to Re: Using multliple formats when writing to a file by hippo
in thread Using multliple formats when writing to a file by rlemert

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.