Re: In which packages can an interface be extended?

> So what you want is to have two independent interfaces, and in a
> third package declare than actually one implements the other, right? 
> Do you have a canonical example where this is useful?

AspectOrientedMultiMethodExample - the scenario was reusing a vendor
defined interface with an interface defined by the enterprise,
at-the-same-time keeping vendor code separate from enterprise code. 

> >This works fine:
> >   package vendor;
> >   import main;
> >   interface main.ITest implements IVendor;

> Yes, that's akin to implementing abstract interfaces.

That's hidden magic ;-)

Given that we need to qualify ITest to main.ITest, it feels like we
should be able to keep the code in a separate package of extensions to
the enterprise code, and qualify both:

   package patches;
   import main;
   import vendor;
   interface main.ITest implements vendor.IVendor;

> Those restrictions are actually not the right ones, but this did not
> seem to be a priority to work on that.

Seems like something to add to the "restrictions" on the wiki and in
the manual.

__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click