Sujet : Re: Threads across programming languages
De : Keith.S.Thompson+u (at) *nospam* gmail.com (Keith Thompson)
Groupes : comp.lang.cDate : 30. May 2024, 23:21:53
Autres entêtes
Organisation : None to speak of
Message-ID : <87ttif0zda.fsf@nosuchdomain.example.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
User-Agent : Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Malcolm McLean <
malcolm.arthur.mclean@gmail.com> writes:
On 24/05/2024 00:31, Keith Thompson wrote:
Obviously, and I can't figure out why you feel the need to make that
point. Of course the phrase "pointer object" doesn't mean "pointer
value". I didn't suggest that it could, or that anyone might think it
could.
A "pointer object" would be the physical bits which hold the
pointer. A "pointer value" would be the address which these bits
represent. You very rarely need to make this distinction because it's
usually quite obvious from context, or it doesn't matter. So usually
the term "pointer" will do. But just occasionally yu might need to be
clear which one you are referring to.
An "object" is by definition a "region of data storage in the execution
environment, the contents of which can represent values".
A "value" is by definition the "precise meaning of the contents of an
object when interpreted as having a specific type". (IMHO this is a
slightly flawed definition; it doesn't cover the value that results from
evaluating an expression. But the definition of "expression" does say
that it specifies computation of a value.)
I'm not sure what you intended to add to the discussion.
-- Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.comvoid Void(void) { Void(); } /* The recursive call of the void */Guilty, Guilty, Guilty!