From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52438) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ya1Um-0007IE-IN for qemu-devel@nongnu.org; Mon, 23 Mar 2015 08:30:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ya1Uj-0000fL-CR for qemu-devel@nongnu.org; Mon, 23 Mar 2015 08:30:16 -0400 Received: from cantor2.suse.de ([195.135.220.15]:59318 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ya1Uj-0000f3-5f for qemu-devel@nongnu.org; Mon, 23 Mar 2015 08:30:13 -0400 Message-ID: <55100750.7050704@suse.de> Date: Mon, 23 Mar 2015 13:30:08 +0100 From: =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] RFC: memory API changes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , QEMU Developers Cc: "Edgar E. Iglesias" , Peter Crosthwaite , Paolo Bonzini , Richard Henderson , Greg Bellows Am 23.03.2015 um 13:24 schrieb Peter Maydell: > * address_space_rw &c to be renamed: > address_space_rw -> as_rw_buf > address_space_read -> as_read_buf > address_space_write -> as_write_buf > address_space_map -> as_map_buf &c > This is just so the names line up nicely and we have a > clear indication that this is a family of functions How does address_space_* not indicate they are a family? address_space_ is much more intuitive to read than shortening it to as_, which can confusingly be read as another English word. Regards, Andreas --=20 SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=C3=BCrnberg, Germany GF: Felix Imend=C3=B6rffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu, Graham Norton; HRB 21284 (AG N=C3=BCrnberg)