> > Larry mumbled something like "implements" and "interface". So to say > > > > package Net::FTP::Foo implements Net::FTP; > > > > But I don't think, anybody wrote an RFC about the plan. > > I did. Or something like it. And I've got a couple of modules on CPAN > (that I really must document better) that kind of work already: > > package ShoppingBasket; > > use ex::interface qw/add_entry total_price delete_entry .../ Interfaces are tricky. One must assume a common agreed-upon vocabulary or ontology. What does 'add_entry' mean, really and exactly? What arguments does it take? What arguments could it take? What does it return? Does it have non-local effects? -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologist word we use for 'stable'. # It is 'dead'. -- Jack Cohen
- RFC on Coexistance and simulaneous use of multiple modul... Garrett Goebel
- Re: RFC on Coexistance and simulaneous use of multi... Michael G Schwern
- Re: RFC on Coexistance and simulaneous use of m... Andreas J. Koenig
- Re: RFC on Coexistance and simulaneous use ... Piers Cawley
- Re: RFC on Coexistance and simulaneous ... Jarkko Hietaniemi
- Re: RFC on Coexistance and simulan... Piers Cawley
- Re: RFC on Coexistance and simulaneous ... Michael G Schwern
- Re: RFC on Coexistance and simulaneous ... Steve Simmons
- Re: RFC on Coexistance and simulan... Paul Johnson
- Re: RFC on Coexistance and sim... Branden
- Re: RFC on Coexistance and... Paul Johnson
- Re: RFC on Coexistance and... Steve Simmons
- Re: RFC on Coexistance and... Paul Johnson
- Re: RFC on Coexistance and... Steve Simmons
- Re: RFC on Coexistance and... David Grove