I want to create a multiform Perl Tk application where each form is defined by two physical files. One file controls the appearnce of the form, and the other controls the functionality.

I was thinking of having each file with the same name, but different extensions, then calling them with "require". In each file would be the "package" key word identifying the name of the form as an object.

Recently I was told not to use "require" and only use "use", but from what I can tell "use" requires a ".pm" extension and the name of the file is the name of the package. So how do I use "use" on two files that I want the same namespace?



UPDATE: Thanx for everyones help. As a matter of fact, many of the forms need only be loaded when they are required, so I may use a mix of the approaches suggested.


In reply to 1 Object 2 Files by AllenG

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.