lanl/singularity-eos

Inconsistent naming conventions of class member variables / C++ standards violations

Ouverte

#255 ouverte le 18 avr. 2023

 (1 commentaire) (2 réactions) (0 personne assignée)C++ (21 forks)auto 404
clean-upgood first issuehelp wanted

Métriques du dépôt

Stars
 (36 étoiles)
Métriques de merge PR
 (Métriques PR en attente)

Description

Within the context of singularity-eos we have different conventions for naming private variables which are members of classes. For nearly all of the analytic EOSs (for which I was mostly responsible) we use a leading underscore for private member variables. In such class scope, this is allowed under the standard, but only if the next character is neither an underscore nor a capital letter. This is part of C++ standards, and while it is likely to work without issue, it's technically reserved.

I propose changing all of the private member variables to trailing underscores, which is consistent with the tabular EOS implementations (both spiner and EOSPAC) and is not standards violating.

Guide contributeur