<div dir="ltr">I think we can just add it to <a href="http://llvm.org/docs/CodingStandards.html">LLVM Coding Standards</a> page. I think part of why it's not used more often is that people just don't know about it, so that would help increase the visibility for everyone.</div><br><div class="gmail_quote"><div dir="ltr">On Fri, Nov 11, 2016 at 10:51 AM Jim Ingham <<a href="mailto:jingham@apple.com">jingham@apple.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is it worthwhile having some place where we can put this sort of policy so people don't have to follow our mailing list to know this sort of rule? The coding conventions were one possible site, but that fell victim to the code reformat...<br class="gmail_msg">
<br class="gmail_msg">
Jim<br class="gmail_msg">
<br class="gmail_msg">
> On Nov 11, 2016, at 9:11 AM, Zachary Turner <<a href="mailto:zturner@google.com" class="gmail_msg" target="_blank">zturner@google.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> Yea, I agree doing it for a whole class at a time should be the standard<br class="gmail_msg">
> On Fri, Nov 11, 2016 at 9:10 AM Jim Ingham <<a href="mailto:jingham@apple.com" class="gmail_msg" target="_blank">jingham@apple.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> > On Nov 10, 2016, at 8:57 PM, Zachary Turner via lldb-commits <<a href="mailto:lldb-commits@lists.llvm.org" class="gmail_msg" target="_blank">lldb-commits@lists.llvm.org</a>> wrote:<br class="gmail_msg">
> ><br class="gmail_msg">
> > Maybe just inline the initializations so we don't have to repeat code across multiple constructors? i.e.<br class="gmail_msg">
> ><br class="gmail_msg">
> > bool m_is_resolved = false;<br class="gmail_msg">
> ><br class="gmail_msg">
> > in the header file.<br class="gmail_msg">
><br class="gmail_msg">
> I actually like the ability to do this in the header file, that seems clearer to me. But if we're going to start doing this more widely I think it would be better to do it consistently - maybe converting on a class by class basis when you touch one of the ivars in the class? Having to look in two places for all these default initializations with only history as the pattern seems like it will make the code harder to read.<br class="gmail_msg">
><br class="gmail_msg">
> Jim<br class="gmail_msg">
><br class="gmail_msg">
><br class="gmail_msg">
> ><br class="gmail_msg">
> > On Thu, Nov 10, 2016 at 8:54 PM Sam McCall via lldb-commits <<a href="mailto:lldb-commits@lists.llvm.org" class="gmail_msg" target="_blank">lldb-commits@lists.llvm.org</a>> wrote:<br class="gmail_msg">
> > sammccall created this revision.<br class="gmail_msg">
> > sammccall added a subscriber: lldb-commits.<br class="gmail_msg">
> ><br class="gmail_msg">
> > Fix uninitialized members.<br class="gmail_msg">
> ><br class="gmail_msg">
> ><br class="gmail_msg">
> > <a href="https://reviews.llvm.org/D26528" rel="noreferrer" class="gmail_msg" target="_blank">https://reviews.llvm.org/D26528</a><br class="gmail_msg">
> ><br class="gmail_msg">
> > Files:<br class="gmail_msg">
> > source/Host/common/FileSpec.cpp<br class="gmail_msg">
> > source/Target/Process.cpp<br class="gmail_msg">
> ><br class="gmail_msg">
> ><br class="gmail_msg">
> > Index: source/Target/Process.cpp<br class="gmail_msg">
> > ===================================================================<br class="gmail_msg">
> > --- source/Target/Process.cpp<br class="gmail_msg">
> > +++ source/Target/Process.cpp<br class="gmail_msg">
> > @@ -4581,7 +4581,7 @@<br class="gmail_msg">
> > : IOHandler(process->GetTarget().GetDebugger(),<br class="gmail_msg">
> > IOHandler::Type::ProcessIO),<br class="gmail_msg">
> > m_process(process), m_read_file(), m_write_file(write_fd, false),<br class="gmail_msg">
> > - m_pipe() {<br class="gmail_msg">
> > + m_pipe(), m_is_running(false) {<br class="gmail_msg">
> > m_pipe.CreateNew(false);<br class="gmail_msg">
> > m_read_file.SetDescriptor(GetInputFD(), false);<br class="gmail_msg">
> > }<br class="gmail_msg">
> > Index: source/Host/common/FileSpec.cpp<br class="gmail_msg">
> > ===================================================================<br class="gmail_msg">
> > --- source/Host/common/FileSpec.cpp<br class="gmail_msg">
> > +++ source/Host/common/FileSpec.cpp<br class="gmail_msg">
> > @@ -278,8 +278,8 @@<br class="gmail_msg">
> > }<br class="gmail_msg">
> ><br class="gmail_msg">
> > FileSpec::FileSpec()<br class="gmail_msg">
> > - : m_directory(), m_filename(), m_syntax(FileSystem::GetNativePathSyntax()) {<br class="gmail_msg">
> > -}<br class="gmail_msg">
> > + : m_directory(), m_filename(), m_is_resolved(false),<br class="gmail_msg">
> > + m_syntax(FileSystem::GetNativePathSyntax()) {}<br class="gmail_msg">
> ><br class="gmail_msg">
> > //------------------------------------------------------------------<br class="gmail_msg">
> > // Default constructor that can take an optional full path to a<br class="gmail_msg">
> ><br class="gmail_msg">
> ><br class="gmail_msg">
> > _______________________________________________<br class="gmail_msg">
> > lldb-commits mailing list<br class="gmail_msg">
> > <a href="mailto:lldb-commits@lists.llvm.org" class="gmail_msg" target="_blank">lldb-commits@lists.llvm.org</a><br class="gmail_msg">
> > <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits</a><br class="gmail_msg">
> > _______________________________________________<br class="gmail_msg">
> > lldb-commits mailing list<br class="gmail_msg">
> > <a href="mailto:lldb-commits@lists.llvm.org" class="gmail_msg" target="_blank">lldb-commits@lists.llvm.org</a><br class="gmail_msg">
> > <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits</a><br class="gmail_msg">
><br class="gmail_msg">
<br class="gmail_msg">
</blockquote></div>