Re: Top 10 Worst C# Features

["G.B." <bauhaus@futureapps.invalid>]

On 03.09.15 11:26, Dmitry A. Kazakov wrote:
> 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.

Yes. Perhaps I should first say what "event" is to name.
(The word being used in different contexts, AFAICT.)
Extensionally, an event is something that happens at some
point in the lifetime of an object, such as being passed,
or one of its operations being called (maybe for the 'Nth
time).

> Either a type exists or it does not.

Yes.

> Furthermore a type is immutable
> throughout all its life,

Yes.

> An object of a type is *same* in all contexts, because the type is same.

While an object doesn't change either identity or type,
it does changes state. This is an event, too.

> What you propose is not typed.

I think that what you might have misunderstood is not typed. :-)

> 2. Regarding finalization, another crucial point. Finalization is *not* an
> operation.

I'm not asking for finalization as an operation.
I'm asking for clearly defined hooks made for operations
(or something else) for what programmers will now put into
Finalize, since there is nothing else where to put it.