Skip to content

Multiple MATLAB engines #19

@bbarker

Description

@bbarker

We could switch to using engOpenSingleUse as the default, as I believe it is a better (safer) default that would allow for Haskell-managed concurrent programming. I suppose we could migrate the existing engOpen-using functions to another name, though I can't immediately think of a good use of them other than to communicate with other applications via MATLAB.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions