The Matlab Component Bindings provide language bindings to Matlab for the Component Interface. 1258 is the current Matlab binding and should be used for all new Matlab components. This allows you to author your component as a Matlab function that receives events from the framework. Matlab developers will find this approach much more natural, and much less work, than authoring a C component.
As with all the bindings, you should create a new Process for this binding using the BRAHMS Manager, which will be based on the template.
- Since Matlab is not a compiled language, certain types of processes authored in Matlab may run slower (including, much slower) than if they had been written in a compiled language.
- Since interfacing with Matlab through the Matlab Engine can be slow, lightweight processes authored in Matlab may run slower (including, much slower) than if they had been authored directly in Matlab. Experience suggests that processes authored against 1262 will tend to incur much less overhead, comparatively, than processes authored against 1258. A future Matlab binding may reduce this overhead.
- Since Matlab does not currently provide a thread-safe engine, processes authored against these bindings cannot be run concurrently in the same memory space (this will be enforced by the framework). They can be run concurrently in different memory spaces using Concerto, however. See Usage Notes (1258) for more details.