Hi list,
I'm trying to get the concept of creating a super class for my
application and understand what elements need to be included in the
base application module.
Let's say I want to create a web app called MyApp. My Directory
structure looks like this ...
/MyApp
Base.pm
On 4/24/06, Ed Pigg [EMAIL PROTECTED] wrote:
Hi list,
I'm trying to get the concept of creating a super class for my
application and understand what elements need to be included in the
base application module.
Let's say I want to create a web app called MyApp. My Directory
structure looks
Cees Hek wrote:
Yes, except that in your subclass example, the fact that you create a
new 'cgiapp_init' method will override the 'cgiapp_init' method in
your base class. That means the 'cgiapp_init' method in your base
class will not get executed. That may be desired, but if it is not,
Michael wrote:
Cees Heek wrote:
Yes, except that in your subclass example, the fact that you create a
new 'cgiapp_init' method will override the 'cgiapp_init' method in
your base class. That means the 'cgiapp_init' method in your base
class will not get executed. That may be desired, but if
On 4/24/06, Ed Pigg [EMAIL PROTECTED] wrote:
So how I put things like session initialization, database connection,
etc.. in the SUPER::cgiapp_init sub. So my SUB CLASS would be
something like
sub cgiapp_init {
my $self = shift;
$self-SUPER::cgiapp_init(@_);
Cees Hek wrote:
On 4/24/06, Ed Pigg [EMAIL PROTECTED] wrote:
So how I put things like session initialization, database connection,
etc.. in the SUPER::cgiapp_init sub. So my SUB CLASS would be
something like
sub cgiapp_init {
my $self = shift;
On Apr 24, 2006, at 12:56 PM, Michael Peters wrote:
Cees Hek wrote:
On 4/24/06, Ed Pigg [EMAIL PROTECTED] wrote:
So how I put things like session initialization, database
connection,
etc.. in the SUPER::cgiapp_init sub. So my SUB CLASS would be
something like
sub cgiapp_init {
my
