in reply to Re: Good programming practice
in thread Good programming practice

Sweet - that answers one part of my question. Didn't know about use vars.

I'm still interested in knowing if this is the best design for such a system.

Jason

wog - I ran out of votes, but there's tomorrow!

Replies are listed 'Best First'.
(jeffa) 3Re: Good programming practice
by jeffa (Bishop) on Nov 03, 2001 at 21:08 UTC
    i do have a problem with require - it's a bit old, and more importantly, it's not portable. If you design a CPAN style module, you can install it on any system and access it from any program. Then you can 'use' the much better:use jdb; instead of require.

    A great reference for building CPAN style modules can be found here: perlnewmod (and no, you don't have to submit your module to CPAN for it to be a CPAN style module).

    But first, read perlmod. :)

    jeffa

[reply]
[d/l]
      If you install the module in the @INC path you can require jbd; the same as use, but without the side effect of being done at compile time. If the module depends on runtime data (like $database from the example) swiching to use may cause trouble.
[reply]
[d/l]

In Section Seekers of Perl Wisdom