Inheritance/Multiple

Inheritance/Multiple
You are encouraged to solve this task according to the task description, using any language you may know.

Multiple inheritance allows to specify that one class is a subclass of several other classes. Some languages allow multiple inheritance for arbitrary classes, others restrict it to interfaces, some don't allow it at all.

Write two classes (or interfaces) Camera and MobilePhone, then write a class CameraPhone which is both a Camera and a MobilePhone.

There is no need to implement any functions for those classes.

Ada

Ada 2005 has added interfaces, allowing a limited form of multiple inheritance. <lang ada>package Multiple_Interfaces is

  type Camera is tagged null record;
  type Mobile_Phone is limited Interface;
  type Camera_Phone is new Camera and Mobile_Phone with null record;

end Multiple_Interfaces;</lang>

Aikido

Aikido does not support multiple inheritance, but does allow multiple implementation of interfaces. <lang aikido> interface Camera { }

interface Mobile_Phone { }

class Camera_Phone implements Camera, Mobile_Phone { }

</lang>

C++

<lang cpp>class Camera {

 // ...

};

class MobilePhone {

 // ...

};

class CameraPhone:

 public Camera,
 public MobilePhone

{

 // ...

};</lang>

C#

In C# you may inherit from only one class, but you can inherit from multiple interfaces. Also, in C# it is standard practice to start all interface names with a capital 'I' so I have altered the name of the interface. In the example we inherit from a class and an interface.

<lang csharp>interface ICamera {

   // ...

}

class MobilePhone {

   // ...

}

class CameraPhone: ICamera, MobilePhone {

   // ...

}</lang>

Clojure

<lang Clojure>(defprotocol Camera)

(defprotocol MobilePhone)

(deftype CameraPhone []

 Camera
 MobilePhone)</lang>

Common Lisp

<lang lisp>(defclass camera () ()) (defclass mobile-phone () ()) (defclass camera-phone (camera mobile-phone) ())</lang>

D

D doesn't allow multiple inheritance, but you can inherit after multiple interfaces.

<lang d>interface Camera {

   // member function prototypes and static methods

}

interface MobilePhone {

   // member function prototypes and static methods

}

class CameraPhone: Camera, MobilePhone {

   // member function implementations for Camera,
   //   MobilePhone, and CameraPhone

}</lang> D also supports template mixins and alias this (multiple alias this are planned) that allows various forms of static composition.

Delphi

Delphi doesn't support multiple inheritance, but it does have multiple interfaces.

<lang Delphi>type

 ICamera = Interface
   // ICamera methods...
 end;

 IMobilePhone = Interface
   // IMobilePhone methods...
 end;

 TCameraPhone = class(TInterfacedObject, ICamera, IMobilePhone)
   // ICamera and IMobilePhone methods...
 end;</lang>

DWScript

See Delphi.

E

E does not have multiple inheritance as a built-in feature. In fact, E only has inheritance at all as a light syntactic sugar over delegation (message forwarding). However, using that facility it is possible to implement multiple inheritance.

This is a quick simple implementation of multiple inheritance. It simply searches (depth-first and inefficiently) the inheritance tree for a method; it does not do anything about diamond inheritance. These shortcomings could be fixed if more powerful multiple inheritance were needed.

<lang e>def minherit(self, supers) {

   def forwarder match [verb, args] {
       escape __return {
           if (verb == "__respondsTo") {
               def [verb, arity] := args
               for super ? (super.__respondsTo(verb, arity)) in supers {
                   return true
               }
               return false
           } else if (verb == "__getAllegedType") {
               # XXX not a complete implementation
               return supers[0].__getAllegedType()
           } else {
               def arity := args.size()
               for super ? (super.__respondsTo(verb, arity)) in supers {
                   return E.call(super, verb, args)
               }
               throw(`No parent of $self responds to $verb/$arity`)
           }
       }
   }
   return forwarder

}</lang>

The task example:

<lang e>def makeCamera(self) {

   return def camera extends minherit(self, []) {
       to takesPictures() { return true }
   }

}

def makeMobilePhone(self) {

   return def mobilePhone extends minherit(self, []) {
       to makesCalls() { return true }
       to internalMemory() { return 64*1024 }
   }

}

def makeCameraPhone(self) {

   return def cameraPhone extends minherit(self, [
       makeCamera(self),
       makeMobilePhone(self),
   ]) {
       to internalMemory() {
           return super.internalMemory() + 32 * 1024**2
       }
   }

}</lang >

And testing that it works as intended:

<lang e> ? def p := makeCameraPhone(p) > [p.takesPictures(), p.makesCalls(), p.internalMemory()]

1. value: [true, true, 33619968]</lang>

Eiffel

<lang eiffel >class

   CAMERA

end</lang> <lang eiffel >class

   MOBILE_PHONE

end</lang> <lang eiffel >class

   CAMERA_PHONE

inherit

   CAMERA
   MOBILE_PHONE

end</lang>

Fantom

Fantom only permits inheritance from one parent class. However, Fantom supports 'mixins': a mixin is a collection of implemented methods to be added to the child class. Any number of mixins can be added to any given child class. It is an error for method names to conflict.

<lang fantom> // a regular class class Camera {

 Str cameraMsg ()
 {
   "camera"
 }

}

// a mixin can only contain methods mixin MobilePhone {

 Str mobileMsg ()
 {
   "mobile phone"
 }

}

// class inherits from Camera, and mixes in the methods from MobilePhone class CameraPhone : Camera, MobilePhone { }

class Main {

 public static Void main ()
 {
   cp := CameraPhone ()
   echo (cp.cameraMsg)
   echo (cp.mobileMsg)
 }

} </lang>

F#

A class can only inherit from one other class, but it can implement any number of interfaces.

<lang fsharp>type Picture = System.Drawing.Bitmap // (a type synonym)

// an interface type type Camera =

 abstract takePicture : unit -> Picture

// a class with an abstract method with a default implementation // (usually called a virtual method) type MobilePhone() =

 abstract makeCall : int[] -> unit
 default x.makeCall(number) = () // empty impl

// a class that inherits from another class and implements an interface type CameraPhone() =

 inherit MobilePhone()
 interface Camera with
   member x.takePicture() = new Picture(10, 10)</lang>

Go

Go abandons traditional object oriented concepts of inheritance hierarchies, yet it does have features for composing both structs and interfaces. <lang go>// Example of composition of anonymous structs package main

import "fmt"

// Two ordinary structs type camera struct {

   optics, sensor string

}

type mobilePhone struct {

   sim, firmware string

}

// Fields are anonymous because only the type is listed. // Also called an embedded field. type cameraPhone struct {

   camera
   mobilePhone

}

func main() {

   // Struct literals must still reflect the nested structure
   htc := cameraPhone{camera{optics: "zoom"}, mobilePhone{firmware: "3.14"}}

   // But fields of anonymous structs can be referenced without qualification.
   // This provides some effect of the two parent structs being merged, as
   // with multiple inheritance in some other programming languages.
   htc.sim = "XYZ"
   fmt.Println(htc)

}</lang> Output: (Note sensor field still blank)

{{zoom } {XYZ 3.14}}

<lang go>// Example of composition of interfaces. // Types implement interfaces simply by implementing functions. // The type does not explicitly declare the interfaces it implements. package main

import "fmt"

// Two interfaces. type camera interface {

   photo()

}

type mobilePhone interface {

   call()

}

// Compose interfaces. cameraPhone interface now contains whatever // methods are in camera and mobilePhone. type cameraPhone interface {

   camera
   mobilePhone

}

// User defined type. type htc int

// Once the htc type has this method defined on it, it automatically satisfies // the camera interface. func (htc) photo() {

   fmt.Println("snap")

}

// And then with this additional method defined, it now satisfies both the // mobilePhone and cameraPhone interfaces. func (htc) call() {

   fmt.Println("omg!")

}

func main() {

   // type of i is the composed interface.  The assignment only compiles
   // because static type htc satisfies the interface cameraPhone.
   var i cameraPhone = new(htc)
   // interface functions can be called without reference to the
   // underlying type.
   i.photo()
   i.call()

} </lang> Output:

snap
omg!

Haskell

<lang haskell>class Camera a class MobilePhone a class (Camera a, MobilePhone a) => CameraPhone a</lang>

Icon and Unicon

Icon does not support classes or inheritance. An intermediate language called Idol was developed as proof of concept for extending Icon. This became one of the major addons contributing to Unicon.

<lang unicon> class Camera (instanceVars)

   # methods...
   # initializer...

end

class Phone (instanceVars)

   # methods...
   # initializer...

end

class CameraPhone : Camera, Phone (instanceVars)

   # methods...
   # initialiser...

end</lang>

Ioke

<lang ioke>Camera = Origin mimic MobilePhone = Origin mimic CameraPhone = Camera mimic mimic!(MobilePhone)</lang>

J

<lang j>coclass 'Camera'

create=: verb define

 NB. creation-specifics for a camera go here

)

destroy=: codestroy

NB. additional camera methods go here

coclass 'MobilePhone'

create=: verb define

 NB. creation-specifics for a mobile phone go here

)

destroy=: codestroy

NB. additional phone methods go here

coclass 'CameraPhone' coinsert 'Camera MobilePhone'

create=: verb define

 create_Camera_ f. y
 create_MobilePhone_ f. y
 NB. creation details specific to a camera phone go here

)

destroy=: codestroy

NB. additional camera-phone methods go here</lang> The adverb Fix (f.) is needed as shown so the superclass constructors get executed in the object, not in the superclass.

Java

Java does not allow multiple inheritance, but you can "implement" multiple interfaces. All methods in interfaces are abstract (they don't have an implementation). When you implement an interface you need to implement the specified methods. <lang java>public interface Camera{

  //functions here with no definition...
  //ex:
  //public void takePicture();

}</lang> <lang java>public interface MobilePhone{

  //functions here with no definition...
  //ex:
  //public void makeCall();

}</lang> <lang java>public class CameraPhone implements Camera, MobilePhone{

  //functions here...

}</lang>

Logtalk

Logtalk supports multiple inheritance. There is no "class" keyword in Logtalk; an "object" keyword is used instead (Logtalk objects play the role of classes, meta-classes, instances, or prototypes depending on the relations with other objects). <lang logtalk>:- object(camera,

   ...).
   ...

- end_object.</lang>

<lang logtalk>:- object(mobile_phone,

   ...).
   ...

- end_object.</lang>

<lang logtalk>:- object(camera_phone,

   specializes(camera, mobile_phone),
   ...).
   ...

- end_object.</lang>

Lua

Lua is prototype-based. A table cannot have more than one metatable, but it can reference more than one in its __index metamethod, by making it a closure.

<lang lua> function setmetatables(t,mts) --takes a table and a list of metatables

 return setmetatable(t,{__index = function(self, k)
   --collisions are resolved in this implementation by simply taking the first one that comes along.
   for i, mt in ipairs(mts) do
     local member = mt[k]
     if member then return member end
   end
 end})

end

camera = {} mobilephone = {} cameraphone = setemetatables({},{camera,mobilephone})

</lang>

Objective-C

Like Java, Objective-C does not allow multiple inheritance, but a class can "conform to" multiple protocols. All methods in protocols are abstract (they don't have an implementation). When you conform to a protocol you need to implement the specified methods.

If you simply want to combine the functionality (method implementations) of multiple classes, you can use message forwarding to mimic the functionality of those classes without actually inheriting them, as described in this guide:

<lang objc>@interface Camera : NSObject { } @end

@implementation Camera @end

@interface MobilePhone : NSObject { } @end

@implementation MobilePhone @end

@interface CameraPhone : NSObject {

 Camera *camera;
 MobilePhone *phone;

} @end

@implementation CameraPhone

-(id)init {

 if ((self = [super init])) {
   camera = [[Camera alloc] init];
   phone = [[MobilePhone alloc] init];
 }
 return self;

}

-(void)dealloc {

 [camera release];
 [phone release];
 [super dealloc];

}

-(void)forwardInvocation:(NSInvocation *)anInvocation {

 SEL aSelector = [anInvocation selector];
 if ([camera respondsToSelector:aSelector])
   [anInvocation invokeWithTarget:camera];
 else if ([phone respondsToSelector:aSelector])
   [anInvocation invokeWithTarget:phone];
 else
   [self doesNotRecognizeSelector:aSelector];

}

-(BOOL)respondsToSelector:(SEL)aSelector {

 return [camera respondsToSelector:aSelector]
 || [phone respondsToSelector:aSelector]
 || [super respondsToSelector:aSelector];  

}

@end</lang>

Caveat: the CameraPhone class will still technically not inherit from either the Camera or MobilePhone classes, so testing a CameraPhone object with -isKindOfClass: with the Camera or MobilePhone classes will still fail.

OCaml

<lang ocaml>class camera =

 object (self)
   (*functions go here...*)
 end</lang>

<lang ocaml>class mobile_phone =

 object (self)
   (*functions go here...*)
 end</lang>

<lang ocaml>class camera_phone =

 object (self)
   inherit camera
   inherit mobile_phone
   (*functions go here...*)
 end</lang>

Oz

<lang oz>class Camera end

class MobilePhone end

class CameraPhone from Camera MobilePhone end</lang>

Pascal

See Delphi

Perl

<lang perl>package Camera;

1. functions go here...

1;</lang>

<lang perl>package MobilePhone;

1. functions go here...

1;</lang>

<lang perl>package CameraPhone; use Camera; use MobilePhone; @ISA = qw( Camera MobilePhone );

1. functions go here...

1;</lang>

or

<lang perl>package CameraPhone; use base qw/Camera MobilePhone/;

1. functions go here...</lang>

The same using the MooseX::Declare extention: <lang perl>use MooseX::Declare;

class Camera {

   # methods ...

} class MobilePhone {

   # methods ...

} class CameraPhone extends(Camera, MobilePhone) {

   # methods ...

}</lang>

Perl 6

Works with: Rakudo Star version 2010.07

<lang perl6>class Camera {} class MobilePhone {} class CameraPhone is Camera is MobilePhone {}

say ~CameraPhone.^parents; # undefined type object say ~CameraPhone.new.^parents; # instantiated object</lang>

Output:

Camera() MobilePhone() Any() Mu()
Camera() MobilePhone() Any() Mu()

PicoLisp

<lang PicoLisp>(class +Camera)

(class +MobilePhone) \

Pop11

<lang pop11>;;; load object support lib objectclass;

define :class Camera;

  ;;; slots go here

enddefine;

define :class MobilePhone;

  ;;; slots go here

enddefine;

define :class CameraPhone is Camera, MobilePhone;

  ;;; extra slots go here

enddefine;

methods go here</lang>

PureBasic

Using the open-source precompiler SimpleOOP. <lang PureBasic>Class Camera EndClass

Class Mobil EndClass

Class CameraMobile Extends Camera Extends Mobil EndClass</lang>

Python

<lang python>class Camera:

 pass #functions go here...</lang>

<lang python>class MobilePhone:

 pass #functions go here...</lang>

<lang python>class CameraPhone(Camera, MobilePhone):

 pass #functions go here...</lang>

Ruby

Ruby does not have multiple inheritance, but you can mix modules into classes: <lang ruby>module Camera

 # define methods here

end class MobilePhone

 # define methods here

end class CameraPhone < MobilePhone

 include Camera
 # define methods here

end</lang>

Slate

<lang slate>define: #Camera. define: #MobilePhone. define: #CameraPhone &parents: {Camera. MobilePhone}.</lang>

Tcl

Works with: Tcl version 8.6

or

Library: TclOO

<lang tcl>package require TclOO

oo::class create Camera oo::class create MobilePhone oo::class create CameraPhone {

   superclass Camera MobilePhone

}</lang>