[fpc-devel] class abstract, class sealed implementation. please review.

[Marco van de Voort]

In our previous episode, Paul Ishenin said:
> 
> > For delphi compatibility we only need to skip it. I agree mostly with Jonas
> > here, I think this is one of those access control things added by popular
> > demand (because language xxx has it).
> 
> Maybe in open source world sealed classes has small meaning since you 
> can always change the code. But even then they have a warning function.
> 
> But they do their security role very good when you distribute your code 
> in the binray form.

> Except the security role sealed and abstract classes have their 
> important oop meaning. Look at the next "phones example":

I don't believe in that magnitude of control, and for meaning we typically
use comments, not language features.

> After all, nobody ask to use sealed/abstract classes as much as 
> possible. If you don't like them - just don't use them. Why to limit 
> other developers?

Yeah I know. That is always the excuse for all extensions.