Skip to content

Conversation

@c-w
Copy link
Contributor

@c-w c-w commented May 22, 2018

Without reading the code closely, it's not entirely obvious at first sight what PIPNAME represents. For example, a possible tokenization of that variable name can lead to the question "What is a PIP and why does it have a NAME?" Expanding the P abbreviation in the variable name to PUBLIC makes the name more immediate and therewith makes it easier to skim the code snippet.

Without reading the code closely, it's not entirely obvious at first sight what `PIPNAME` represents. Expanding the `P` abbreviation in the variable name to `PUBLIC` makes the name more immediate and therewith makes it easier to skim the code snippet.
@PRMerger7
Copy link
Contributor

@c-w : Thanks for your contribution! The author, @neilpeterson, has been notified to review your proposed change.

@neilpeterson
Copy link
Contributor

@c-w thanks a bunch.

#sign-off

@ktoliver ktoliver merged commit 7fa9ed0 into MicrosoftDocs:master May 23, 2018
@c-w c-w deleted the patch-1 branch May 23, 2018 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants