(As you can probably see, usually I am too lazy to write down my ideas. I used to keep them in my mind for plenty of time until they become clear enough to be written down quickly as implementation codes. But from time to time, I am asked what is the development plans for Dao or what are the planned features. So I might begin to write down some ideas down from time to time. Hope that there will be some interesting feedbacks.)

The following I am going to write is already ready for implementation. It will be a type called interface , which can be related to prototype oriented programming.

An interface is defined as a set of member methods which can be called upon an object. Similar to class , interface will support inheritance, and can declare member methods. But it will not allow implementation of its member methods.

Example,

Then one can bind an interface to a class or wrapped C/C++ type (possibly also tuple type) by,
So that, the compatibility of MyClass with InterfaceA will be checked at compiling time. Then at running time, when an instance of MyClass is passed to something that need InterfaceA type, it will only be necessary to check if InterfaceA has been bind to MyClass . In this way, detailed checking of the member methods of MyClass against the interface will not be necessary. In places an InterfaceA is needed, anything (unrelated classes or C/C++ types) has InterfaceA bound to can be used. For running time binding of interfaces, there will be a standard method std.bind() .

Other planned things include more support for operator overloading and bindings to OpenSSL library etc.