Re: [cgiapp] Re: RFC - C::A::Plugin - abstract base class for plugins

[Bill Catlan <suppressed>]

> > >>Maybe this... (as I said above)
> > >>   use CGI::Application::Plugin::TT ( name =>
> tt,
> > >>override => 0);
> > > 
> > > 
> > > Yes, default behavior for
> > > 
> > >   use CGI::Application::Plugin::TT
> > > 
> > > being:
> > > 
> > >   use CGI::Application::Plugin::TT ( name =>
> > > [moniker], override => 1 );
> > 
> > That sounds good to me. Also, I would think that
> all
> > plugins 
> > should have those defaults as well (if we decide
> to
> > use 
> > UNIVERSAL::moniker default namespace).
> 
> Doesn't your agreement here contradict your above
> statement that the default namespace would be the
> module?
> 

Plus, I think most plugin methods will /not/ seek to
override existing methods, and will be of the
"cgiapp_plugin_available" type.  I think, where a name
is not provided by the user, it is more consistent and
intutitive that those methods would be put in a
default namespace, not the module's namespace.  This
further differentiates the cgiapp_plugin_available
attribute from the cgiapp_plugin_override attribute -
which I think makes sense.

Bill


---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed