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

2000-08-15 Thread Chaim Frenkel
As much as I'm not for it, would having sub foo :method {} # In objects vtbl and sub foo {} # only if procedural call being a valid construct and having perl dispatch appropriately, be viable? chaim "GB" == Graham Barr [EMAIL PROTECTED]

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

2000-08-15 Thread Chaim Frenkel
"GB" == Graham Barr [EMAIL PROTECTED] writes: GB On Tue, Aug 15, 2000 at 10:14:36AM -0400, Chaim Frenkel wrote: As much as I'm not for it, would having sub foo :method {} # In objects vtbl and sub foo {} # only if procedural call being a valid construct

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

2000-08-15 Thread Tim Bunce
On Mon, Aug 14, 2000 at 11:30:28AM -0500, Jonathan Scott Duff wrote: I'll just make up some alternatives for everyone to shoot at: use Foo;# like CGI.pm, morphs on demand use Foo;# procedural Foo use OOFoo;

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

2000-08-15 Thread Michael Fowler
On Tue, Aug 15, 2000 at 12:33:15PM +0100, Tim Bunce wrote: On Mon, Aug 14, 2000 at 11:30:28AM -0500, Jonathan Scott Duff wrote: use Foo;# like CGI.pm, morphs on demand use Foo;# procedural Foo use OOFoo; #