what you say make sense, it is just not true for Pd. in object oriented programming (and maybe other programming too) the instantiation of a "class" is called object. but referring to the miller's pd documentation (html) there are no classes, and he calls classes "objects". '"reference" patches, one for each kind of object in Pd'. so even if there is the technical differentiation between that not instantiated thing, usually called "class" and the instance of it, called "object", that naming convention is not true for Pd. both, the "class" and the instance are known as "object". marius.
Roman Haefeli wrote:
On Wed, 2007-09-12 at 22:13 +0200, Steffen wrote:
On 12/09/2007, at 21.47, Roman Haefeli wrote:
at least in my opinion the differentiation between a [dac~] and the 'dac~' in general is quite important.
I would love some insight on that. If you or anyone would care to elaborate?
sorry, the [dac~] vs. 'dac~ in general' wasn't a good example at all.
actually it is pretty simple. what i meant here was the distinction between the class 'dac~' and the object 'dac~'. the object 'dac~' is an intantiation of the class 'dac~', whereas the class 'dac~' is what you would describe in pdpedia.
the term 'class' somehow covers all capabilities, that 'dac~' does provide you. you can decide to make use of these capabilities by creating an object [dac~ 2 4], which is another object than [dac~ 1 3] (or even another object than another [dac~ 2 4]).
actually, you never see a class, you just know, that it exists, but you probably see many [objects] of this class.
roman
___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de