Re: technical correctness
"Joshua Maurice" <joshuamaur...@gmail.com> wrote in message
To add nothing to this otherwise useless conversation of this thread:
This entire argument is one over the definition of the term "a part
of". Let me take a stab at it. Consider the following:
class Foo { void bar(){} };
Foo x;
In the common, standard, etc., abstraction and terminology of C++ and
statically typed programming languages - it's quite silly to say that
Foo::bar is a part of x. This is an argument over definition, and thus
I have only two options - appeal to authority, or appeal to consensus.
Either way, for any reputable authority and any relevant consensus, I
win.
In short, "a part of" implies some sort of containment or ownership
relation. A class does "contain and "own" its member functions - a
member function is contained by exactly one class, and it makes sense
only in the context of that class. An object does not "contain" nor
"own" its type, and an object does not "contain" nor "own" its
associated member functions - there often are multiple objects of a
specific type or a specific member function. Thus member functions are
not part of objects, in the common lingo.
On Jan 5, 6:58 am, "Paul" <pchris...@yahoo.co.uk> wrote:
If a child is PART OF a sunday school group there is no containment or
ownership.
To be PART OF a group does not imply containment or ownership as you seem=
to
think. Your definintion of "PART OF" is very wrong as would your definiti=
on
of anything else probably be.
That's the problem. "A part of" is rather ambiguous and has overloaded
meanings.
A school group is an aggregation of children. Thus the children are "a
part of" the school group. A class is an aggregation of its members
and a name. Thus it seems right to say that the members are "a part
of" the class.
However, that still doesn't really work well because of the domain
specific usage. The domain is C++, and to a lesser extent all
statically typed programming languages. In that domain specific
discourse, to say X is a part of an object implies that X resides in
the memory region of that object, or there is some ownership
relationship via encapsulation.