Re: Top 10 Worst C# Features

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On Thu, 3 Sep 2015 10:14:35 +0200, Georg Bauhaus wrote:

> What finalization can presumably solve I'd love to see addressed
> systematically, using language that attaches life cycle events to
> types.

What a horrific idea...

> Is it possible to produce a scheme that makes attaching "event
> subprograms", say, well defined? Maybe permissions would be based
> on visibility of entities referred to?

No.

1. Regarding types there is no any events. It must be clearly understood.
Either a type exists or it does not. Furthermore a type is immutable
throughout all its life, which is extremely important for substitutability.
An object of a type is *same* in all contexts, because the type is same.
What you propose is not typed.

2. Regarding finalization, another crucial point. Finalization is *not* an
operation. The object ceases to exist after its finalization. Therefore
exist certain composition rules of how finalization is defined upon type
operations such as aggregation, inheritance etc.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de