On Jun 19, 2010, at 8:46 PM, Mathieu Bouchard wrote:
On Sat, 19 Jun 2010, Hans-Christoph Steiner wrote:
I am saying that each class should have a function called setup().
That's how it works in Max/MSP.I know what you're saying. And I think that whatever it is in Max/ MSP is informative, but it doesn't have to be like that. I don't
especially care what they actually do. Sometimes it's a good
inspiration, but you've got to have a better reason than "it's like
that in Max/MSP". I wouldn't actually even list it in a list of
reasons for doing something, except when making a compatibility
library.And then, as I just explained, there are many things that you just
can't achieve by considering that the only thing one would ever do
is install a new class.Some other examples are : the code that adds an inlet to the builtin
comment class. the code that adds extra menu items in the Help menu.
Iemguts modifying the savefn and propertiesfn of the canvas class.
etc.I think that having a single function called setup() load multiple
classes is not a good idea.Classes in other programming languages are rarely bundled as
separate files. In C and C++, it's usually one big .so file for a
large collection of classes. Even in Java, the paradise of class- files, it didn't take long before people begged that the class-files
be joined together into a few big files, and that's how the JAR
format was born.
A JAR is a .zip file of a folder with individual .class files, one for
each class.
.hc
Using ReBirth is like trying to play an 808 with a long stick. - David Zicarelli