Re: Re: Pan 0.14.2 Won't Compile

On Monday 30 July 2007 04:33:22 Duncan wrote:
> Greg Lee <greg-Hlp6T+piA/[email protected]> posted
> [email protected], excerpted below, on  Mon, 30 Jul 2007 06:01:56
>
> +0000:
> > On Sun, 29 Jul 2007 13:33:11 -0500, Michael Satterwhite wrote:
> >> msort.c: In function ‘msort_with_tmp’: msort.c:68: error: invalid
> >> lvalue in increment msort.c:69: error: invalid lvalue in increment
> >> msort.c:74: error: invalid lvalue in increment msort.c:75: error:
> >> invalid lvalue in increment
> >>
> >> Looking at the source to msort.c, this appears to be occurring in the
> >> use of an incremented pointer to a pointer.
> >
> > I suspect this is due to some change in gcc 4.1.2, since I've seen the
> > compiler complaint several times recently.  You could just recode the
> > increment as a separate statement.  But better to get a more recent
> > version of Pan (which no longer has an msort.c, since it's written in
> > c++).
>
> I'll second that.  pan 0.14.x is what, something like four years old
> now?  (Just checked, almost, 0.14.2 was released on August 31, 2003, so
> it's just about a month short of four years.  Time does fly...)  It's
> unsurprising newer and stricter gccs don't like the old code.
>
That seems reasonable ... but ...

If 0.14.2 is not the version of pan that should be used, then the website 
shouldn't be recommending it as the stable version. A newer version needs to 
be promoted to stable, and a new fork made for beta work.