On Tue, Aug 15, 2000 at 04:59:19PM -0800, Michael Fowler wrote: > Which makes me think of the following. You don't need to 'use' a seperate > module for a procedural or OO interface. The module author could simply > provide a constructor in the procedural module that would require the OO > module in the background, and bless the object into that class. That was where this thread started. > This would > appear largely transparent to the user, right up until they tried to do > isa() or ref() tests on the object. But that is the catch. Now if the language was to give us a way to support both in the same package in an efficient way, so much the better. Graham.
- Re: How to implement both object->... John Berthels
- Re: How to implement both object... Jonathan Scott Duff
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... Chaim Frenkel
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... Chaim Frenkel
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... John Berthels
- Re: How to implement both ob... Tim Bunce
- Re: How to implement both ob... Michael Fowler
- Re: How to implement both ob... Graham Barr
- Re: How to implement both ob... David L. Nicol
- Re: How to implement both ob... Tim Bunce
- Re: How to implement both ob... Graham Barr
- Re: How to implement both object->meth... Michael Fowler
- Re: How to implement both object->meth... Chaim Frenkel
- Re: How to implement both object->... Hildo Biersma
- Re: How to implement both object->method and m... Graham Barr
- Re: How to implement both object->method and module... Nick Ing-Simmons
- Re: How to implement both object->method and module... Michael Fowler