What's the difference between an object and a type?

[Dylan]

thanks

[Jacques Labuschagne]

Dylan wrote:

thanks

An object is an instance of a type.

Jacques.

[Jonathan Turkanis]

It's like the difference between a boxer and a weight class, or an employee and
a job description.

Jonathan

[Rafal 'Raf256' Maj]

sp******@ontheb all.com news:39******** *************** *********@4ax.c om

thanks

The same as between "a humen" and "the Dylan".

--
~~~~=~~~~l_;~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~
_|\___J \____, Pozdrawiam, moje www, C++, kontakt, itd.:
X-( ssn256 ) Rafal Maj Raf256 - http://www.raf256.com/me-news/
,"-------------" (strona w budowie)

[Rafal 'Raf256' Maj]

sp******@ontheb all.com news:39******** *************** *********@4ax.c om

thanks

The same as between "a humen" and "the Dylan".

typo... *human*
--
~~~~=~~~~l_;~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~ ~~~~~~~~
_|\___J \____, Pozdrawiam, moje www, C++, kontakt, itd.:
X-( ssn256 ) Rafal Maj Raf256 - http://www.raf256.com/me-news/
,"-------------" (strona w budowie)

[Jon Bell]

In article <39************ *************** *****@4ax.com>,
Dylan <sp******@onthe ball.com> wrote:

thanks

object :: type == cookie :: cookie-cutter

--
Jon Bell <jt*******@pres by.edu> Presbyterian College
Dept. of Physics and Computer Science Clinton, South Carolina USA

[Dave O'Hearn]

What's the difference between "int" and "5"?

The question is rather vague. I don't know if it has an answer.
Philosophers have debated this stuff for thousands of years and show no
sign of stopping soon.

When inheritence comes in, it is important not to confuse the different
relationships. The type-instance relationship is not the same as the
base-derived relationship. Sometimes people will get sloppy and use the
phrase "is a" to describe all these relationships, like 'file' is an
fstream, fstream is an ifstream, etc. They are two different things.
--
Dave O'Hearn

[Howard]

"Dave O'Hearn" <da******@pobox .com> wrote in message
news:11******** **************@ f14g2000cwb.goo glegroups.com.. .

What's the difference between "int" and "5"?

The question is rather vague. I don't know if it has an answer.
Philosophers have debated this stuff for thousands of years and show no
sign of stopping soon.
They have? I don't recall any such discussions. For example, "what's the
difference between 'human" and "Bob'?" One is a description/definition, the
other names a specific instance.

I see no confusion (or vagueness) here at all. An object is an instance of
a type. A type is a description (a declaration), which follows very cleary
defined rules in the C++ language. There are built-in types and
user-defined types. Since this question is asked in the C++ language
newsgoup, it seems pretty clear that these are the definitions asked for.

When inheritence comes in, it is important not to confuse the different
relationships. The type-instance relationship is not the same as the
base-derived relationship. Sometimes people will get sloppy and use the
phrase "is a" to describe all these relationships, like 'file' is an
fstream, fstream is an ifstream, etc. They are two different things.
--
That's a rather confusing analogy. The "is a" relationship described public
inheritance, only. What this has to do with types and objects is, well,
nothing as far as I can see...?
Dave O'Hearn

No offense intended, Dave, but I think you're just going to confuse the
newbie here. Philosophy and C++ don't mix very well, in my opinion. :-)

-Howard

[jeffc]

"Howard" <al*****@hotmai l.com> wrote in message
news:dO******** **************@ bgtnsc04-news.ops.worldn et.att.net...

When inheritence comes in, it is important not to confuse the different
relationships. The type-instance relationship is not the same as the
base-derived relationship. Sometimes people will get sloppy and use the
phrase "is a" to describe all these relationships, like 'file' is an
fstream, fstream is an ifstream, etc. They are two different things.
--

That's a rather confusing analogy. The "is a" relationship described public
inheritance, only. What this has to do with types and objects is, well,
nothing as far as I can see...?

Agreed. "Is a" makes sense in both contexts, even though it means 2 different
things.

[Dave O'Hearn]

Howard wrote:

I see no confusion (or vagueness) here at all. An object is an
instance of a type. A type is a description (a declaration), which
follows very cleary defined rules in the C++ language. There are
built-in types and user-defined types. Since this question is asked
in the C++ language newsgoup, it seems pretty clear that these are
the definitions asked for.
Exactly. I see no confusion either, but the OP is confused. How?
No offense intended, Dave, but I think you're just going to confuse
the newbie here. Philosophy and C++ don't mix very well, in my
opinion. :-)

Almost. I was trying to show the OP that his question was confusing,
not to confuse the OP. The difference between a type and an object
should be obvious to everyone, no technical background required. If it
isn't obvious, there is probably some confusion in terms. But I can't
guess what that confusion is. It would help if he asked a more specific
question about objects and types. (Un)fortunately , if this is a
homework, he may not be able to.

--
Dave O'Hearn