Re: [PHP-DEV] Re: [PHP-CVS] cvs: php4 /tests/classes interface_class.phpt interface_doubled.phpt interface_implemented.phpt interface_instantiate.phpt interface_member.phpt interface_method.phpt interface_method_final.phpt interface_method_private.phpt interface_must_be_implemented.phpt

At 21:12 12.03.2003, Shane Caraveo wrote:
>An interface should not implement an interface, only classes should 
>implement interfaces.  'implement' infers that actual executable code is 
>provided that implements an interface.  Again, I haven't followed the 
>interface stuff, and sorry for writting without reading the background, 
>but I'm working off the assumption that interfaces are kind of like IDL.

We do not force classes to directly implement (supply code) for an 
interface method (and i do like that (now)).

>ok:
>interface extends interface
>class extends class implements interface
>
>not ok:
>interfaces implements interface
>class extends interface

I would favor this:
interface [ implements interface+ ]
class [ extends class ] [ implements interface+ ]

or less:
interface [ extends interface+ ]
class [ extends class ] [ implements interface+ ]

I like the former more because it separates classes to extends and 
interfaces to implements
and does not suggest MI. Howeve the latter has some more kind of logic 
since an interface
"extends" other interfaces when they are inherited. (Maybe i'll change my 
mind after sleeping it
over).

i'm sure you know to write it correctly with the missing ',' :-))

marcus