API changes in R2019a?

2 次查看（过去 30 天）
Bo
Bo 2019-7-30
评论： James Tursa 2019-7-31
I have a (Win64) C# software package allowing users to transfer data to MATLAB for user defined processing through a MATLAB script and transfer back the results.
It relies on the MATLAB API with libeng.dll etc, and was working fine with R2018b, but has stopped working with R2019a. I changed nothing, so assume something changed with the MATLAB API, but can find no mention of such a change here or on the 'News' pages.
Any bright ideas?
  1 个评论
James Tursa
James Tursa 2019-7-30
Did you recompile it with R2019a, or are you using the previously compiled code?

请先登录，再进行评论。

请先登录，再回答此问题。

回答（1 个）

James Tursa
James Tursa 2019-7-30
I don't know if this is the cause of your problems, but there was a change to the low level mxArray variable structure in R2019a. So code might have to be recompiled in order to work.
  5 个评论
显示 3更早的评论
Bruno Luong
Bruno Luong 2019-7-31
OK so they change the order of the fields. I can't see the motivation. The aligment is more or less identical for 64-bit pointer (all MATLAB) no?
That looks odd.
James Tursa
James Tursa 2019-7-31
Since ClassID and VariableType are both ints they occupy 4 bytes each. Having them next to each other means they won't mess up any 8-byte boundary alignments for the stuff around them. So, yes, I agree that the compiler won't need to add any padding in either the old or the new definitions to maintain 8-byte boundary alignments of the nearby fields.
Motivation for the change? I suppose the new definition looks nicer having the crosslink stuff next to each other. But I suspect the real motivation is just to irritate me and mess up my mex hacking code ...

请先登录，再进行评论。

类别

在 Help Center 和 File Exchange 中查找有关 RESTful API 的更多信息

标签

产品

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by