"Michael Peters" <[EMAIL PROTECTED]> ???????/???????? ? ???????? ?????????: news:[EMAIL PROTECTED] > > > Viacheslav Sheveliov wrote: >> I'd like to add. >> >> It's like in Exporter: we make declarations of @EXPORT* vars and >> Exporter makes the work for us. > > Exporter works that way cause you *subclass* it and override the @EXPORT* > variables. The way Dispatch currently works all you need to do is > *subclass* it > and override the dispatch_args() method. Same principle.
One little difference. You advocate creating new separate module/method. I do for defining interface data in C::A module. Not so important, what it be - variable, sub or constant (however last two are better, I think). Dispatcher or C::A base class can "makes the work for us" - define runmodes, dispatch requests. > I like the idea of overriding a method better since you can more > complicated/dynamic stuff than you can with simple variable assignment. > > -- > Michael Peters > Developer > Plus Three, LP > > > --------------------------------------------------------------------- > Web Archive: http://www.mail-archive.com/[email protected]/ > http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
