From octave-maintainers-request at bevo dot che dot wisc dot edu Fri Dec  6 20:47:19 2002
Subject: Re: CVS Octave is now Pix-free
From: Paul Kienzle <pkienzle at jazz dot ncnr dot nist dot gov>
To: "John W. Eaton" <jwe at bevo dot che dot wisc dot edu>
Cc: Andy Adler <adler at site dot uottawa dot ca>,    octave-maintainers mailing list <octave-maintainers@bevo.che.wisc.edu>
Date: Fri, 6 Dec 2002 21:46:46 -0500

What to check for is pretty easy: the octave header that is no longer.

mex doesn't care what it uses since it is not sharing the data with Octave.  
Indeed, it should be using a set rather than a list since I want to check 
membership, add, remove and clear.  There is no inherent ordering to the data.

 - Paul

On Fri, Dec 06, 2002 at 04:38:27PM -0600, John W. Eaton wrote:
> On  6-Dec-2002, Andy Adler <adler at site dot uottawa dot ca> wrote:
> 
> | My only issue is that if we check in these changes now,
> | then octave-forge will not build with any "released" version
> | of octave.
> | 
> | I suppose we could always refer people to the released octave
> | forge packages - but I suspect we'll have many people
> | writing to the octave mailing list with complaints.
> 
> The patches for the sparse package are fairly small and simple, so I
> suppose we could go ahead and make the changes in octave-forge and
> then include the reverse set of patches with octave-forge for a while,
> so people will know what to do.  Or, since the changes are so simple,
> I suppose we could put in some kind of #ifdef so that it would work in
> either case.  I'm not sure exactly what to check for, but if you think
> it is important enough, we could probably come up with something.
> 
> jwe
>