Date: Sat, 2 Feb 2008 04:13:02 -0800 From: Alfred Perlstein <alfred@freebsd.org> To: Hans Petter Selasky <hselasky@freebsd.org> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 129920 for review Message-ID: <20080202121301.GY99258@elvis.mu.org> In-Reply-To: <200802020818.57037.hselasky@freebsd.org> References: <200712020001.lB201XbN000811@repoman.freebsd.org> <20080202022234.GR99258@elvis.mu.org> <200802020818.57037.hselasky@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Hans Petter Selasky <hselasky@freebsd.org> [080201 23:18] wrote: > On Saturday 02 February 2008, Alfred Perlstein wrote: > > This change makes very little sense. If xfer->frbuffers is a bare > > pointer, then why add 0 to it? Just pass xfer->frbuffers or use a > > macro that explains what you are doing. > > > > I can change those to a plain "xfer->frlengths". It was just a reminder for > me, because some places we use "xfer->frlengths + 1" and "xfer->frbuffers + > 1". > > I will write a script that converts all of those. What does '+ 1' mean? Is it something special like a channel or something? If so it should be a macro that's more descriptive. -- - Alfred Perlstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080202121301.GY99258>