What distinguishes an interface from an abstract class in Avaloq Script?

An interface distinguishes itself from an abstract class primarily by defining a contract for classes that implement it, while an abstract class can provide both complete and incomplete implementations of methods. In Avaloq Script, an interface only includes method signatures and does not offer any implementation itself; this serves as a guideline for other classes to follow.

By contrast, an abstract class can contain implemented methods as well as abstract methods (those without implementation). This allows developers to provide a default implementation of certain behaviors that can be reused by subclasses or leave the provision of specific implementations to be defined in the subclasses. Essentially, the core difference lies in the role each plays: interfaces are purely about enforcing a set of behaviors (the contract), while abstract classes can enforce behavior while also allowing for shared code.

This distinction highlights the design principles in object-oriented programming, where interfaces emphasize flexibility and abstraction, and abstract classes provide a balance between abstraction and code reuse.