Multiple MATLAB engines
Opened this issue · 0 comments
bbarker commented
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.