# Marking class with no abstract methods as an abstract

Consider an interface:

public interface IWindowOperations
{
// Some operation methods.
}


Class definitions:

1. public abstract class BaseWindow<T> : IWindowOperations
{
// partially implemented class.
}

2. public class TraditionalWindow<T> : BaseWindow<T>
{
// Fully implemented class.
}

3. public class ModernWindow<T> : BaseWindow<T>
{
// Fully implemented class.
}


(1) is already marked as an abstract so it cannot be instantiated. (2) and (3) are fully implemented though they should not be instantiated, rather they should be derived by other class specifying <T> so the application framework can register them. e.g.

 public class SliderWindow<Win8> : ModernWindow<Win8>
{
// In general case this is just an empty class
// unless special handling is needed.
}


In this case is it right to mark (2) and (3) as an abstract? Those are just template defining some concrete functionality but also allows derived classes to override if required.

Also, you should probably reflect your intent in class names by adding Base suffix to (2) and (3) (or prefix, but i think it is less common).