Re: How to implement both object-method and module::function interface?

2000-08-09 Thread Bart Lateur
On Wed, 09 Aug 2000 11:41:20 +0100, Hildo Biersma wrote: Could we agree on the idea that CGI.pm should be split up? No. I could agree that CGI-somemethod(@args); would do exactly the same as CGI::somemethod(@args); i.e. no difference between function calls and class methods,

Re: How to implement both object-method and module::function interface?

2000-08-09 Thread Bart Lateur
On Wed, 09 Aug 2000 13:58:34 +0100, Hildo Biersma wrote: Yikes. Class method calls should perform inheritance, subroutine calls should not. I agree with that. Altering the language to make the two look the same is a bad idea, because it breaks, fatally, as soon as the class supports more than

Re: How to implement both object-method and module::function interfa ce?

2000-08-09 Thread Hildo Biersma
Chaim Frenkel wrote: "HB" == Hildo Biersma [EMAIL PROTECTED] writes: HB There's a reason people use objects - if only to give the user a handle HB to wrap the module's state. Any module that supports both OO and HB procedural usage is basically a singleton - only one instance exists at

Re: How to implement both object-method and module::function interfa ce?

2000-08-09 Thread Chaim Frenkel
"HB" == Hildo Biersma [EMAIL PROTECTED] writes: HB There's a reason people use objects - if only to give the user a handle HB to wrap the module's state. Any module that supports both OO and HB procedural usage is basically a singleton - only one instance exists at HB any one time (at least in