Skip to content

DOC: Remove mistaken exception to data member initialization guideline #196

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dzenanz merged 1 commit into from
Jan 19, 2023
Merged

DOC: Remove mistaken exception to data member initialization guideline #196

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 0 additions & 13 deletions SoftwareGuide/Latex/Appendices/CodingStyleGuide.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1621,19 +1621,6 @@ \section{Initialization and Assignment}
\end{minted}
\normalsize

Nevertheless, there may be some exceptions to the initialization list rule. In
some situations where it can be foreseen that the corresponding
\code{Set\#\#name} or \code{\#\#nameOn}/\code{\#\#nameOff} may be

\begin{itemize}
\item overloaded by some classes in the future, or
\item deprecated, and a warning thrown when it is called to help migration,
\end{itemize}

initialization through the corresponding \code{Set\#\#name} or
\code{\#\#nameOn}/\code{\#\#nameOff} method is recommended instead of directly
manipulating the data member.

Smart pointers need not to be initialized, since they initialize themselves
to the \code{null} pointer, so they are the sole exception to the above rule.

Expand Down