On Mon, Sep 18, 2000 at 10:16:46AM -0400, John Porter wrote: > Hildo Biersma wrote: > > IMHO, mixing procedural and OO interfaces to the same module is a bad > > idea. Promoting it in the language is not wise. > > O.k., but that's not the same as disallowing it. Perl is not a B&D > language. I'd just like to second John here. I've got a couple of modules where the OO and functional interfaces happen to mesh together beautifully (Class::Fields is one). CGI.pm isn't exactly the greatest example of a combination of the two styles... but from the holy wars which rage between C<$cgi->param('foo')> and C<param('foo')> regularly, I can see why it is desired. But it doesn't have to be easy. -- Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED] Just Another Stupid Consultant Perl6 Kwalitee Ashuranse But why? It's such a well designed cesspool of C++ code. Why wouldn't you want to hack mozilla? -- Ziggy
- RFC 223 (v1) Objects: C<use invocant> pragma Perl6 RFC Librarian
- Re: RFC 223 (v1) Objects: C<use invocant> p... John Porter
- Re: RFC 223 (v1) Objects: C<use invocant> p... Damian Conway
- Re: RFC 223 (v1) Objects: C<use invocant> p... Nathan Wiger
- Re: RFC 223 (v1) Objects: C<use invocant&g... Hildo Biersma
- Re: RFC 223 (v1) Objects: C<use invoca... John Porter
- Re: RFC 223 (v1) Objects: C<use in... Hildo Biersma
- Re: RFC 223 (v1) Objects: C<u... John Porter
- Re: RFC 223 (v1) Objects: C&... Michael G Schwern
- Re: RFC 223 (v1) Objects... Graham Barr
- Backtracing contexts with self($n) (was R... Nathan Wiger
- Re: Backtracing contexts with self($n... Hildo Biersma
- Re: Backtracing contexts with se... John Porter
- Re: RFC 223 (v1) Objects: C<use invocant&g... Philip Newton
- Re: RFC 223 (v1) Objects: C<use invocant> p... Graham Barr
- Re: RFC 223 (v1) Objects: C<use invocant&g... John Porter
- Re: RFC 223 (v1) Objects: C<use invocant> p... Piers Cawley