From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: MIME-Version: 1.0 References: <20190107105214.GA31559@kroah.com> <20190107130314.GD3200@kadam> <20190114105123.GA22496@kadam> In-Reply-To: <20190114105123.GA22496@kadam> From: Himadri Pandya Date: Mon, 14 Jan 2019 17:39:24 +0530 Message-ID: Subject: Re: rtl8192e: need help with variable naming convention Content-Type: multipart/alternative; boundary="0000000000001f12b2057f69eb45" List-ID: To: Dan Carpenter Cc: Greg KH , driverdev-devel@linuxdriverproject.org --0000000000001f12b2057f69eb45 Content-Type: text/plain; charset="UTF-8" On Mon, 14 Jan, 2019, 4:21 PM Dan Carpenter normally obvious it's an array because of the [] characters. > Okay. How about renaming it to "_list[ ]" ? But I'm not sure if calling it a list will introduce redundancy or increase readability by showing we're implementing a list with an array? - Himadri > --0000000000001f12b2057f69eb45 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, = 14 Jan, 2019, 4:21 PM Dan Carpenter <dan.carpenter@oracle.com wrote:

Naming is hard.=C2=A0 Having "_array" in the name isn't great= either.=C2=A0 It's
normally obvious it's an array because of the [] characters.

Okay. How a= bout renaming it to "_list[ ]" ? But I'm not sure if calling = it a list will introduce redundancy or increase readability by showing we&#= 39;re implementing a list with an array?=C2=A0

<= /div>
- Himadri=C2=A0
--0000000000001f12b2057f69eb45--