[PD-dev] PureUnity now includes an "external"

Mathieu Bouchard matju at artengine.ca
Sat Jan 7 18:54:29 CET 2006


On Sat, 7 Jan 2006, Hans-Christoph Steiner wrote:
> 
> Because when you mix up files of different types, it makes the pattern
> matching rules more complicated.  I am sure there are other reasons as
> well, that's the first that comes to mind.

Does it? wow. Then how come there are so many *.pd files in the 
/externals/ module ?

Also, I'm curious about how you would break down pureunity into individual 
externals. Several "classnames" defined in it are aliases 
(class_addcreator) but not aliases of classes defined in PureUnity! 
they're aliases for internal classes, e.g.:

[f.inlet] is same as [inlet]
[~.inlet] is same as [inlet~]

Would each call to class_addcreator have to go in a separate C file?

 _ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju
| Freelance Digital Arts Engineer, Montréal QC Canada




More information about the Pd-dev mailing list