Re: Re: CGI::Application vs CGI::Builder

How does CGI::Builder provide better superclassing than CGI::Application? I'm really confused about this statement. My runmodes go through two superclasses (at least!) before hitting CGI::Application, each providing some layer of useful stuff.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

Comment on Re: Re: CGI::Application vs CGI::Builder

Replies are listed 'Best First'.
Re: Re: Re: CGI::Application vs CGI::Builder by Anonymous Monk on May 03, 2004 at 20:29 UTC
An example: http://search.cpan.org/~domizio/CGI-Builder-1.2/lib/CGI/Builder.pm#Overrunning	[reply]
You have written Perl6's method invocation in Perl5? by dragonchild (Archbishop) on May 03, 2004 at 21:21 UTC
So, basically, you provide something similar to the method invocation magic that Perl6 will be providing. Interesting ... Would you be able to extract that code out and provide it to the community? I know I would love to have my hands on that kind of code before Perl6 ... ------ We are the carpenters and bricklayers of the Information Age. Then there are Damian modules.... sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon.* - flyingmoose	[reply]
Re: You have written Perl6's method invocation in Perl5? by Anonymous Monk on May 04, 2004 at 12:52 UTC
I know I would love to have my hands on that kind of code before Perl6 ... Well, this gives you what you want ;-) `use CGI::Builder qw\| Your::SuperClass Your::OtherSuperClass \|;` [download] Would you be able to extract that code out and provide it to the community? I thinked about the possibility to put that system in a general module, but I didn't find a (simple) way to do it. I don't think it's easy to 'extract' because it's simple, but very specific to the CGI::Builder (and extensions) process. Anyway, if you want to see it yourself, the whole CGI::Builder code is just around 200 lines, so you could easily inspect it. I think the most important parts to look in the code are: sub CGI::Builder::_::exec (that executes the handlers in the classes) sub import (which sets the hash returned by the overrun_handler_map) overrun_handler_map (Class::groups) Domizio Demichelis	[reply] [d/l]