<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p> </p>
<p style="margin-bottom: 0in; line-height: 100%"><font size="-1">
+1 for doing it all at once but with the following suggestion,
which
is basically that we need to manage the scale of issues that may
crop
up in a gradual manner.</font></p>
<font size="-1">
</font>
<p style="margin-bottom: 0in; line-height: 100%"><font size="-1">Run
the renaming
program on the whole of the current latest stable code. That
result
can be uploaded and release-tested that will give a better idea
of
issues. That is, the issue rate for the changed code over the
unchanged release code.</font></p>
<font size="-1">
</font>
<p style="margin-bottom: 0in; line-height: 100%"><font size="-1">When
the prior issue
volume becomes acceptable, run the changed code in the buildbots
to
collect more issues.</font></p>
<font size="-1">
</font>
<p style="margin-bottom: 0in; line-height: 100%"><font size="-1">When
that issue
volume becomes acceptable, the changed release becomes the
latest
release.</font></p>
<font size="-1">
</font>
<p style="margin-bottom: 0in; line-height: 100%"><font size="-1">At
that point those
working on their own code copies can diff their changes to the
release before the
changed release. They can then run the renaming on their own
code and
diff that result to the changed release. Those two diffs should
align
and it would be nice to have a tool that could verify that, but
the
diff lengths should not be that hard to manually check.</font></p>
<p style="margin-bottom: 0in; line-height: 100%"><font size="-1">Maintaining
the new standard might be done by running the renaming on new
submissions and counting the changes, with any changes recorded
and provided to the author for correction.<br>
</font></p>
<p style="margin-bottom: 0in; line-height: 100%"><font size="-1">Regards,
Neil Nelson<br>
</font></p>
<font size="-1">
</font>
<p>
<style type="text/css"><font size="-1">p { margin-bottom: 0.1in; line-height: 115%; background: transparent none repeat scroll 0% 0%; }</font></style></p>
<div class="moz-cite-prefix"><font size="-1">On 7/18/19 7:09 PM,
Chris Lattner via llvm-dev wrote:</font><br>
</div>
<blockquote type="cite"
cite="mid:8F88B748-6E4A-45C6-BBA0-D444AF829971@nondot.org">
<blockquote type="cite" class="">
<div class=""><font size="-1">On Jul 18, 2019, at 3:49 PM, Rui
Ueyama via llvm-dev <<a
href="mailto:llvm-dev@lists.llvm.org" class=""
moz-do-not-send="true">llvm-dev@lists.llvm.org</a>>
wrote:</font></div>
<br class="Apple-interchange-newline">
<div class="">
<blockquote class="gmail_quote" style="caret-color: rgb(0, 0,
0); font-family: Helvetica; font-size: 12px; font-style:
normal; font-variant-caps: normal; font-weight: normal;
letter-spacing: normal; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; word-spacing:
0px; -webkit-text-stroke-width: 0px; text-decoration: none;
margin: 0px 0px 0px 0.8ex; border-left-width: 1px;
border-left-style: solid; border-left-color: rgb(204, 204,
204); padding-left: 1ex;">
<div class="" lang="PL">
<div class="gmail-m_-6468609924593710405WordSection1">
<p class="MsoNormal"><span style="color: rgb(31, 73,
125);" class="" lang="EN-US">And one more question:</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73,
125);" class="" lang="EN-US">What is the plan of
renaming variables in llvm and clang? Will it be
done gradually, i.e. directory by directory?</span></p>
</div>
</div>
</blockquote>
<div style="caret-color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; text-decoration: none;"
class=""><br class="">
</div>
<div style="caret-color: rgb(0, 0, 0); font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; word-spacing: 0px;
-webkit-text-stroke-width: 0px; text-decoration: none;"
class="">That's a big topic. I was thinking of starting a
new thread just for that. Originally I was trying to do this
directory-by-directory basis, but now I'm inclined to do
this in a single extremely large patch. There's a risk of
doing this that way (in particular, I'm not confident that I
can keep the buildbots green or will be able to make them
green in a timely manner after committing), but I think that
will make downstream repo maintainer's work easier.</div>
</div>
</blockquote>
</blockquote>
</body>
</html>