mxArray is defined as an incomplete type in the API header files, hence the prohibition against declaring an mxArray type ... only a pointer is allowed. That being said, you can define your own type that resembles an mxArray header struct and then use some type punning to get at the innards of an mxArray. For an example of that you can see this submission:
But using your own mxArray definition ignores the MATLAB Memory Manager. If you create your own mxArray type and then define some variables using it, they will not be accounted for properly by the Memory Manager or in the garbage collection lists. Any attempt to use these variables in a MATLAB function, or returning them to a workspace, would risk crashing MATLAB.
Is there some particular reason why you think you need an mxArray variable (not just a pointer)? Unless you are doing something exotic, one would rarely need a variable of type mxArray ... you typically only need to work with pointers to them.
