Wow. I missed that completely. Found some doc in What's New and FMAC
Code:
The new Composite class is a class that instantiates child objects. Syntactically, the class looks like an object, as nested child objects are placed
immediately inside the composite. At runtime, the composite behaves more like a class, as it is instantiated the same way as a class. A composite
can have child objects, methods and properties. Methods and properties can also be defined in child objects. Construct_Object and
End_Construct_Object cannot be defined on a composite.
Code:
// Composite(_Class):
//
// This is a type of class. You can create instances of it, but you define it like an object.
// With all it's benefits e.g. nested objects, properties, procedures in those objects etc.
//
// There is but one downside and that is like any object the instance the procedures have to be registered.
// It should not give much overhead but, to be aware of it...
Frank Cheng