From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [edk2-devel] [edk2-CCodingStandardsSpecification PATCH 2/2] Source Files / Spacing / Multi-line func. calls: allow condensed arguments To: Laszlo Ersek ,devel@edk2.groups.io From: "Chang, Abner" X-Originating-Location: TW (185.221.70.44) X-Originating-Platform: Windows Chrome 107 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Sat, 12 Nov 2022 17:35:36 -0800 References: <922996c2-e60a-80ec-6d4a-8b2e5a639c9b@redhat.com> In-Reply-To: <922996c2-e60a-80ec-6d4a-8b2e5a639c9b@redhat.com> Message-ID: <25893.1668303336748921539@groups.io> Content-Type: multipart/alternative; boundary="x3wVlYwokF9eJobXwpAl" --x3wVlYwokF9eJobXwpAl Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all, As we are going to release CCS 2.3, we would like to address some pending i= ssues of CCS. For this, I think we can, - Still keep the one line per argument style in CCS although the multi-argu= ments in the one line style can cover this. This avoids confusion from read= ers and questions about if they can do the one-line per argument style. - If the arguments are in different lines, the first argument must be inden= ted with two spaces from the start of the function name or the member funct= ion name. How is this? Abner --x3wVlYwokF9eJobXwpAl Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi all,
As we are going to release CCS 2.3, we would like to address s= ome pending issues of CCS. For this, I think we can,
- Still keep the = one line per argument style in CCS although the multi-arguments in the one = line style can cover this. This avoids confusion from readers and questions= about if they can do the one-line per argument style.
- If the argume= nts are in different lines, the first argument must be indented with two sp= aces from the start of the function name or the member function name.
= How is this?

Abner --x3wVlYwokF9eJobXwpAl--