StackData macro not generated for C++

2 views (last 30 days)
Hi,
we are using matlab coder to generate C-code according to defined function interface, we use this to develop stand alone libraries with different functionality. Sometimes the C-functions that are generated takes a variable <function_name>StackData as first parameter, this can be detected via generated macro called typedef_<function_name>StackData. The type of this variable and the macro are specifed in a file called <function_name>_types.h. Including this file and checking if this macro exists allows us to write code which always adhere to the signature of the function. So far all is good.
Some time ago I wanted try to generate C++ code: and also when generating C++ code the functions sometimes takes the <function_name>StackData as first argument, however there are NO macro defined which allows us to detect this, hence I can not adhere to the signature of the function. This is effectively keeping us from generating C++ code, which would be more suitable as this is what the surrounding software is written in.
Is the fact that no macro is generated in C++ mode a bug? Or is there another explanation for this...
BTW, I am using R2019b.
  2 Comments
Alexander Söderqvist
Alexander Söderqvist on 29 Apr 2021
Edited: Alexander Söderqvist on 29 Apr 2021
The struct, when needed as first argument to the function, is generated also in C++ mode, yes. However in C-mode I also get a macro generated, which allows me to detect whether the function actually takes the struct as first argument or not. This is how it looks in C-mode, and what I would expect also from C++-mode:
#ifndef typedef_fooStackData
#define typedef_fooStackData
typedef struct {
struct {
double foovar[968256];
} f0;
} fooStackData;
#endif /*typedef_fooStackData*/

Sign in to comment.

Accepted Answer

Ryan Livingston
Ryan Livingston on 29 Apr 2021
Edited: Ryan Livingston on 30 Apr 2021
It is by design that the typedef guards are not present in C++. The use case you describe here is not one we had in mind for them. The fact that the generated function changes signature in an unpredictable manner seems like the root issue to me. We've made an internal note for the MATLAB Coder team to look at addressing this in the future.
Since you're in R2019b and interested in C++, I'd suggest taking a look at the ability to package the generated code into a class rather than free functions. That will give you a class with one or more entry-point methods which are independent of the stackData argument. That data will be stored as a class property thereby giving you a consistent interface.
cfg.CppInterfaceStyle = 'Methods';
cfg.CppInterfaceClassName = 'Interface';
codegn -config cfg ...
will enable that and produce a class like:
class Interface
{
public:
Interface();
~Interface();
real_T entryPointFunction(real_T n);
fStackData *getStackData();
private:
fStackData SD_;
};
Where entryPointFunction is your entry-point. Then, on the calling side you can instantiate the object and just call the method without having to pass stackData.

More Answers (0)

Tags

Products


Release

R2019b

Community Treasure Hunt

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

Start Hunting!

Translated by