Skip to content

CPP: QLDoc enhancements #2309

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.

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
merged 54 commits into from
Nov 15, 2019
Merged

CPP: QLDoc enhancements #2309

merged 54 commits into from
Nov 15, 2019

Conversation

geoffw0
Copy link
Contributor

@geoffw0 geoffw0 commented Nov 13, 2019

This is Zem's PR [CPP-418] QLDoc enhancements with some additional fixes:

  • fixed merge conflicts, including significant changes to qldoc in TypedefType.qll
  • addressed remaining unresolved comments
  • added a couple of missed backticks

zlaski-semmle and others added 22 commits November 12, 2019 16:47
… figure out how to describe unknown and erroneous types.)
…sorted complex number operations, where surface syntax could not be determined.
          assorted complex/imaginary arithmetic operations.
@geoffw0 geoffw0 added the C++ label Nov 13, 2019
@geoffw0 geoffw0 requested a review from a team as a code owner November 13, 2019 10:44
*/
abstract class Assignment extends Operation {
/** Gets the lvalue of this assignment. */
/** Gets the *lvalue* of this assignment. */
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can anyone remember whether we decided to keep this formatting (*lvalue*)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We decided against formatting code with asterisks, but I think in this case it's meant to denote italics because lvalue is not an English word. Allows writing italics with single asterisks (bold is double asterisks), but it's more consistent if we stick to underscores, changing this to _lvalue_.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've done a search-and-replace to change *lvalue* into _lvalue_ (and similarly for *rvalue* etc).

Copy link
Contributor

@jbj jbj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not done -- I'll continue reviewing later.

@jbj
Copy link
Contributor

jbj commented Nov 13, 2019

I should be clear that none of my comments so far are blocking for this PR.

@@ -7,6 +7,9 @@ abstract class UnaryLogicalOperation extends UnaryOperation { }

/**
* A C/C++ logical not expression.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* A C/C++ logical not expression.
* A C/C++ logical NOT expression.

for consistency

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure I agree with this one. Do we capitalize 'not' anywhere else?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes right below in the same file change "and" to "AND" and "or" to "OR". The same changes are in BitwiseOperation.qll, although bitwise NOT is called complement there.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Which would you prefer? I can make a quick follow-up PR to make this consistent either way.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer NOT because it's consistent with AND/OR and because everyone will understand it.

geoffw0 and others added 22 commits November 14, 2019 11:22
@geoffw0
Copy link
Contributor Author

geoffw0 commented Nov 14, 2019

All comments addressed. I'm on holiday tomorrow so ideally this wants to be merged this evening. I'll keep an eye on it.

@jbj jbj merged commit 73d9cc2 into github:master Nov 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants