On Fri, Apr 28, 2006 at 10:21:43AM -0400, Leonid Grinberg wrote:
>
> Alternatively, you can make a common_functs.pl file, where each one of
> the above actions is performed in a subroutine (the file should only
> have subroutines, and should not do anything outside of them (except
> like use strict;)) and then, from within each file, you could do
> something like
>
> BEGIN
> {
> do ('common_functs.pl');
> die if $@;
> }
Is there some reason in particular you wouldn't use require instead?
It sounds, overall, like the OP is just looking to separate the Model
from the View and Controller functionality to some extent -- but doesn't
yet know it.
--
Chad Perrin [ CCD CopyWrite | http://ccd.apotheon.org ]
unix virus: If you're using a unixlike OS, please forward
this to 20 others and erase your system partition.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
