If you can rely on the fixed offset of the data in a line, unpack, or substr/regex matching will get you the data. It will be easier if you split the file into an array of lines, or else originally slurp it that way,

my @lines = <$handle>;
my %record;
for (@lines) {
    next unless /^\|  (\w+)  \| (\d+)/;
    $record{$1} = $2;
}
[download]

That doesn't just assign one value to one variable which is named after another piece of the data; it associates all those other pieces with their data.

You wind up with a more useful and easier-to-manage representation of the data in your file.

If you're stuck with that scalar variable, you can use the same regex globally,

my %record = $data =~ /^\|  (\w+)  \| (\d+)/g;
[download]

That looks simpler, but it is, IMO, more fragile.

To get exactly what you asked for, knowing the offset and length of the field,

my $rec1ref = \substr $data, $offset, $len;
$$rec1ref = $newval;
[download]

If length($newval) != $len, the offsets to subsequent data will be disturbed and the data seen in $$rec1ref will be truncated or augmented.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.