Date: Fri, 29 Mar 2024 09:25:27 +0000 (UTC) Message-ID: <2138319512.21821.1711704332525@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_21820_821134467.1711704327515" ------=_Part_21820_821134467.1711704327515 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The LSST C++ Coding Style Guidelines are available at C++ Coding Standard. The Rules = provide the look-and-feel of LSST DM coding style and the expectations for = LSST DM statement construction. Recall that C++ Coding Standards Rules fall= into 3 categories:
Refer to C++ Coding Standard#Introduction f= or the Detailed explanation.
To the extent possible, REQUIRED, MUST and SHALL rules will be checked b= y automated software with reports mailed to the developer; SHOULD, RECOMMEN= DED and MAY rules may also be checked by automated software with a separate= report.
Upon receiving a Standards Compliance report, the developer is expected = to resolve the mandatory issues. Many LSST Rules may be 'broken' if the dev= eloper feels there are good reasons for not following the Standards; this c= aveat might be tightened up if the developers aren't primarily holding to t= he Standards.
Steve Bickerton implemented a C++ Coding Standards checker based on Pyth= on regex matching. It implements about 50 of the DM C++ Coding Standards Ru= les.
The code is available from https://dev.lsstcorp.org/c= git/LSST/DMS/devenv/lsst.git/tree/scripts/style.py and may be dire= ctly run on your local system.
Use this tool to check your DM C++ Coding Standards compliance.