You had to be right about this (your explanation was the only one I had and very elegant, to boot), but I couldn't spot where I was reading the changed file back into the array that you read the original into. I thought (could be wrong) I had made a local copy of the @strmeta ("structured metadata") variable for purposes of the deletion bits. I still think you had to be right, but I couldn't find the exact source of the error.

Instead I took George's advice and simply made @strmeta a global variable (er, well, I don't actually know if "global" is the right word--I didn't make a local copy), and didn't reload it after writing it to file, just used the altered @strdata array to print out the changed data. The problem went away!

Thanks very much to everyone!

--ghopper

In reply to Re: Re: Datafile doesn't update before being read by ghopper
in thread Datafile doesn't update before being read by ghopper

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.