Class is what pd calls objects internally. For example here is the setup routine for the unpackOSC object:

void unpackOSC_setup(void) { unpackOSC_class = class_new(gensym("unpackOSC"), (t_newmethod)unpackOSC_new, (t_method)unpackOSC_free, sizeof(t_unpackOSC), 0, 0); class_addlist(unpackOSC_class, (t_method)unpackOSC_list); }

I think of the ideal thing as a 'class' and its instances in a patch as 'objects'. The object receives 'messages' that the class handles using 'methods'.

Martin

marius schebella wrote: as hans already knew, I disagree. I have not heard the term class before. I think the term class is really not in use by pd users. what you (hans) call a class is called an object by everybody else... [class] <-- that is not a class, it is an object. [message( <-- and that is a message. when we are talking about "dac~", then we are talking about the object dac~, even if it is not the technically correct term (I learned now: it is a class, until you make an instance of the class, that is called object) but that is confusing. please use object!

marius.

Hans-Christoph Steiner wrote:

...

Marius and I are sitting here arguing over whether we should use the term "class" or "object" in the pdpedia as the standard term for differentiation, e.g. bang (class) vs. bang (selector).

I think the current usage of the term "object" in Pd has two meanings: an instance of a class, and the class itself. I think we should distinguish between these two in the pd wiki, and the word "class" is quite well established for that.

Yes, that means some education for some users, but that's a big part of the pdpedia mission.

That's my take, Marius will now disagree. :D

.hc

---

Man has survived hitherto because he was too ignorant to know how to realize his wishes. Now that he can realize them, he must either change them, or perish. -William Carlos Williams

---

PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list