Thread Subject: mex files and & operator

Is there some problem with "&" operator and mex compiler? It try to compile for example the following (test.c):


----------------------------------------------------------------------------------------------------
#include "mex.h"

void add_them(double &k,double x, double y)
{
k=x+y;
}

void mexFunction(
    int nlhs, mxArray *plhs[],
    int nrhs, const mxArray *prhs[])
{
  double x,y,k;
     
  // get the inputs
  x=mxGetScalar(prhs[0]);
  y=mxGetScalar(prhs[1]);
    
  
  // call the function
  add_them(k,x,y);

  //create the output
  plhs[0]=mxCreateDoubleScalar(k);
  
  return;
}
------------------------------------------------------------------------------------------------------

and I get:


>>mex test.c
Error test.c: 3 syntax error; found `&' expecting `)'
Error test.c: 3 skipping `&' `k' `,'
Error test.c: 3 missing name for parameter 1 to function `add_them'
Error test.c: 3 syntax error; found `double' expecting `{'
Error test.c: 3 missing identifier
Error test.c: 3 syntax error; found `double' expecting `;'
Error test.c: 3 syntax error; found `)' expecting `;'
Error test.c: 3 skipping `)' `{'
Error test.c: 5 undeclared identifier `k'
Warning test.c: 3 possible usage of y before definition
Warning test.c: 3 possible usage of x before definition
Error test.c: 20 too many arguments to `add_them'
Error test.c: 20 too many arguments to `add_them'
Warning test.c: 12 possible usage of k before definition
11 errors, 3 warnings
------------------------------------------------------------------------------------------------------------------------


Thank you for your time

On 23 Nov, 13:42, "Petros Mpogiatzis" <pain...@geo.auth.gr> wrote:
> Is there some problem with "&" operator and mex compiler?

Depends on what compiler and language you use.

> It try to compile for example the following (test.c):

The .c ending indicates to the compiler that you
want to compile C code, as opposed to C++ or fortran,
or whatever other languages are supported through MEX.
It is your responsibility as programmer to ensure that

1) What you write is indeed valid C code.
2) You use a compiler that supports the language
   features you use in the code. C is a constantly
   evolving language, and not all compilers support
   all features.

> void add_them(double &k,double x, double y)

Don't know what the C99 standard says about this,
but this is not valid pre-C99 C. It is, however,
valid C++. But you already indicated to the compiler
through the .c ending of your file name that you
write C, not C++.

Rune