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
[class.mem, class.mfct.non-static] Convert nonstatic to non-static si… #658
Conversation
\rSec2[class.mfct.non-static]{Nonstatic member functions}% | ||
\indextext{member function!nonstatic} | ||
\rSec2[class.mfct.non-static]{Non-static member functions}% | ||
\indextext{member function!non-static} | ||
|
||
\pnum | ||
A \grammarterm{non-static} member function may be called for an object of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove the bogus \grammarterm while you're here?
I've removed the bogus grammar term. I didn't squash because they seem like unrelated changes, but I can try to squash if you would really like me to. :-P |
No, the two commits are fine now. Does this change require regenerating the grammar and xrefs? |
When I ran latexmk, it did say that it was generating a file for On Tue, Mar 22, 2016 at 2:50 PM, Thomas Köppe notifications@github.com
|
There are "regenerate" guides in the Readme. |
Thank you for the hint about regenerating from the readme, there were indeed modifications which I've added. |
The way |
Richard has fixed something, can you fetch and rebase? Then the makegram script should work better. |
I fetched and rebased, which seems to have removed all the inserted whitespace from f586dad. |
…nce the hyphenated use is the more common term.
My bad, the change doesn't affect the grammar at all, so no need to regenerate anything. As you were. |
…nce the hyphenated use is the more common term.