Les interfaces sont-elles un fléau ou sont-elles mal utilisées ?

There are several considerations
And practices concerning interfaces

Some developers say that interfaces can be used as a replacement of multiple inheritance mechanisms, which cause complexity and ambiguity. But each feature must be implemented each time it is declared: this is not an inheritance, this is a wrapper to the description of a part of a group of classes, like IDisposable. It is the same as a multiple inheritance with one implemented class and some abstract classes: it is a particular case which allows only one way hierarchy with interfaces as abstract connectors that describes services.

Some developers say that interfaces can be used to separate the access to an object of this instance. Historically, interfaces are a COM & DCOM heritage: they are used to manipulate components services, whatever objects are, where they are, and how they are implemented. Interfaces are not a replacement to multiple inheritance, they are something else.

Recommended articles:
A plea for full multiple inheritance support in .NET
A Typed Intermediate Language for Compiling Multiple Inheritance

Lire la suite »

Les défauts d'implémentation du pattern singleton

The paradigm

Consider this common singleton pattern implementation:

The problem is that you can inherit this class and create a public constructor if there is no private constructor. Furthermore, static members are allowed. This is no longer a singleton at all. Setting the class as sealed can be an acceptable solution, but you must implement singleton by singleton, i.e., more than ten lines. Thus, coding a such singleton can be the source of many errors and difficulties. Thinking with factoring is not only an agile principle, it is a mathematical theorem.

Defining a generic singleton

A generic solution is to check the absence of static members and that there is only one parameterless private constructor, or an exception is thrown. Singletons that inherit this class can't be inherited and must be sealed. Moreover, the implementation of singleton types are checked at program startup. Therefore, it is not the best solution, but the only thing to do is to create one parameterless private constructor, no static members, and seal the class.

  Generic Persistent Singleton Sample (53,4 KiB)

Lire la suite »

Situation des développements

Le temps passé sur les projets est d'environ une à deux heures par jour.

L'avancée des fonctionnalités est estimée à 80% :

  • Core : 80%
  • Diagnostics : 75%
  • Diagnostics.Testing : 50%
  • IO : 75%
  • Net.Remoting : 100%
  • Data.Singleton : 90%
  • Data.Embedded : 80%
  • Data.Container : 80%
  • Threading : 90%