-
Notifications
You must be signed in to change notification settings - Fork 16
ENH: Set the preferred Doxygen documentation style explictly. #82
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
ENH: Set the preferred Doxygen documentation style explictly. #82
Conversation
|
@phcerdan following the suggestion I made: Thanks ! |
thewtex
left a comment
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.
Thanks, @jhlegarreta !
Minor grammar note inline.
| extracted and formatted into documentation. | ||
|
|
||
| Note that ITK prefers the backslash (``\\'') style versus the at-sign (``@'') | ||
| style to wrtite the documentation commands. |
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.
wrtite the -> write
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.
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.
e481462 was rebased on master.
e200ea9 to
4cbb0bd
Compare
Set the preferred Doxygen documentation style explicityle following the discussion in: http://review.source.kitware.com/#/c/23399/
4cbb0bd to
e481462
Compare
|
I already approved, but @thewtex's change request is not "outdated". |
|
Matt's change suggestion has already been addressed in e481462. |
|
Sorry for the delay in the follow-up review -- GitHub does not do a good job at sending me emails 😠 |
Set the preferred Doxygen documentation style explicityle following the
discussion in:
http://review.source.kitware.com/#/c/23399/