Re: Is MSDN wrong? or I made a mistake? about static member function

Tech-Archive recommends: Fix windows errors by optimizing your registry

C# further compounds the confusion by having some rule for allocating
some objects on the stack, and some on the heap, and it is not
apparent where your object is.

Yes it is very apparent as you know the type (value or not) of object.

It is necessary to know for deterministic finalization,
something else C# is weak in.

Its not really weak in it. It does provide a way to do it except that
it is not
readily apparent as most of the time you will not need it. However
these issues are not C# specific, rather .Net issues. Language really
has nothing to do with it.

I couldn't care less what the history of the language is, but I find like
the two distinct notations: -> and .

This has no meaning in a pure .Net world. It seems you are comparing
C++ and managed world, which really is comparing apples and oranges.

---
Ajay

.

Relevant Pages

  • Re: Is MSDN wrong? or I made a mistake? about static member function
    ... some objects on the stack, and some on the heap, and it is not ... Yes it is very apparent as you know the type of object. ... but I thought C# allocates classes on the heap and structs on the ... Deterministic finalization is important cleaning up resources (such as ...
    (microsoft.public.vc.mfc)
  • Re: bunch of pedants
    ... <begin quote> ... on the ease with which a stack can be maintained. ... where they describe the stack and its associated register (r13) ... but to refute your apparent belief ...
    (comp.lang.c)
  • Re: SBS2003 Outlook HTTP/RPC not working
    ... you added the v6 stack. ... Mea culpa? ... Let no one missunderstand that the hole in my foot is ... apparent - perhaps not. ...
    (microsoft.public.windows.server.sbs)