C++ MEX与C MEX的区别及MATLAB适配选型咨询

Hey there! Let me break this down for you based on your specific scenario:

Since your core code is a C++ TCP client, the C++-specific MEX documentation is the right pick for you, and here's why:

• Native C++ feature support: It lets you directly use C++ constructs like classes, STL containers, and object-oriented code structures. You won't have to rewrite your existing C++ TCP client into C-style code, which saves a ton of adaptation work.
• Smoother data type interaction: The C++ MEX API (under the matlab::data namespace) offers a more intuitive way to convert between MATLAB arrays and C++ data types. This should directly solve the data type issues you ran into with the general C/C++ MEX examples, which mostly rely on C-style mxArray functions that don't play nice with modern C++ code.
• Simulink S-Function compatibility: C++ MEX files work seamlessly with Simulink S-Functions as long as you follow the S-Function entry point specifications. This aligns perfectly with your plan to use the code in Simulink later.

Bonus tips to avoid common pitfalls #

• When writing your C++ MEX code, make sure to include MATLAB's C++ headers like mex.hpp or matlabengine.hpp depending on your needs.
• Compile with MATLAB's mex command tailored for C++—for example, mex your_cpp_client_mex.cpp for basic MEX files, or add linker flags (-L, -l) if your TCP client depends on external libraries.

内容的提问来源于stack exchange，提问作者Hierend