Subject: Re: curses fix for sysinst
From: David Laight <firstname.lastname@example.org>
Date: 07/29/2003 18:16:08
> > Further thoughts show that this isn't the relevant bug :-(
> > AFAICT this code doesn't have lines != 1 when called by sysinst.
> Well, I don't know if "lines" could ever be other than 1 when calling
> this curses code, but, just in case it was, shouldn't we be using
> memmove(3) rather than memcpy(3)?
winsdelln(win, count) is a published interface....
memcpy() is correct because the memory of adjacent lines isn't contiguous.
There is a loop for each line just above, and two versions of the code,
one for insert the other for delete.
David Laight: email@example.com