I guess I wasn't clear in my post. Now that I read it again I see my mistake. So let me give a more detailed explanation. What I am trying to do is to parse through an html file and create objects (am using the moose module for class creation).

if(...something...) { $n_DT[$count] = DT->new; if($line =~ m/>(.*)</) { $n_DT[$count]->{'ID'} = $1; } ... } elsif(..something else)...) { $r_DT[$count_1] = r_DT->new; if($line =~ m/>(.*)</) { $r_DT[$count_1]->{'ID'} = $1; ... }

The variables n_DT and r_DT are arrays of objects which I want to use/share between the two scripts. I am also saving the two arrays in text files. So I could possibly read the files again to create my list, but I was wondering if there was another, more efficient, way of doing this. Hope this clears my question.


In reply to Re: Destructors and global variables by perl_noob_101
in thread Destructors and global variables by perl_noob_101

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.