R: [PD] Re: [PD-announce] clr: externals in CLR assemblies

[Thomas Grill]

Am 20.01.2006 um 20:33 schrieb Mathieu Bouchard:

> On Fri, 20 Jan 2006, Thomas Grill wrote:
>
>> that's not completely correct: the PD-like style would be to register
>> the class (that's the actual CLR assembly) when loading it the first
>> time. There, a static Main function could be called registering the
>> methods. When creating the CLR object, the constructor is called,
>> registering inlets and outlets. This has the advantage that the 
>> objects
>> would be more lightweight (method table is needed only once per class,
>> not per instance) and that loading is faster.
>
> Wait. Does Davide mean the thing that constructs the objects or the 
> thing
> that constructs the class itself? I seem to recall that in Java the 
> latter
> would be called "static initializers" and would be written like 
> "static{
> blah };", right? What's the CLR-equivalent of that?

don't know what a static initializer is like, but in C# it's like in 
C++. There are static functions that belong to a class, so that there 
is no instance pointer. A reserved one is Main which is normally used 
to bootstrap application classes.

gr~~~