Re: q2c trouble

[John Darrington]

There certainly seems to be something horrible with q2c:

The regression.c generated from your last checkin of regression.q has
this:

static void
free_regression (struct cmd_regression *p UNUSED)
{
  free (p->v_variables);
  free (p->v_variables);
}

which is rather alarming.

I'll see if I can find out what's going on with q2c at the week-end.

In the mean time it might be possible to kludge around this, by
putting something like:

#define free(X) while(0)

into regression.q

J'


On Thu, Mar 09, 2006 at 10:46:25AM -0500, Jason Stover wrote:
     I'm having q2c trouble. The regression
     syntax specification used to say this:
     
            /* (specification)
               "REGRESSION" (regression_):
             *variables=varlist;
              statistics[st_]=r,
              ...
     
     and now it says this
     
         /* (specification)
            "REGRESSION" (regression_):
               *variables=custom;
           statistics[st_]=r,
           ...
     
     in the former case, q2c made struct cmd_regression with a 
     v_variables member. In the new case, it does not, but it
     still generates this instruction in regression.c:
     
     static void
     free_regression (struct cmd_regression *p UNUSED)
     {
        free (p->v_variables);
     }
     
     so now regression.c will not compile since there is no
     member called v_variables in a struct cmd_regression.
     
     -Jason
     
     
     
     _______________________________________________
     pspp-dev mailing list
     address@hidden
     http://lists.gnu.org/mailman/listinfo/pspp-dev

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://pgp.mit.edu or any PGP keyserver for public key.

signature.asc
Description: Digital signature