Skip to content

History / Specification Style Guidelines

Revisions

  • Updated Specification Style Guidelines (markdown)

    @tkoeppe tkoeppe committed Nov 27, 2016
  • Add source code formatting guides.

    @tkoeppe tkoeppe committed Nov 27, 2016
  • Don't suggest "Effects: Behaves the same as: ..."

    @zygoloid zygoloid committed Nov 24, 2016
  • Give an example of the disallowed form "Effects: Equivalent to: return x."

    @zygoloid zygoloid committed Nov 23, 2016
  • Updated Specification Style Guidelines (markdown)

    @tkoeppe tkoeppe committed Nov 18, 2016
  • Update style rules to indicate that "shall" is usually a requirement at the program level, not at the implementation level (the implementation-level requirement is for a diagnostic)

    @zygoloid zygoloid committed Nov 17, 2016
  • Add "Returns" element style.

    @tkoeppe tkoeppe committed Nov 17, 2016
  • Updated Specification Style Guidelines (markdown)

    @burblebee burblebee committed Apr 19, 2016
  • Updated Specification Style Guidelines (markdown)

    @burblebee burblebee committed Apr 19, 2016
  • Updated Specification Style Guidelines (markdown)

    @burblebee burblebee committed Apr 19, 2016
  • Updated Specification Style Guidelines (markdown)

    @burblebee burblebee committed Apr 19, 2016
  • Move some wording guidelines from https://github.com/cplusplus/LEWG/blob/master/library-design-guidelines.md

    @jyasskin jyasskin committed Jul 4, 2014
  • Let statements in function descriptions

    @sdutoit sdutoit committed Feb 13, 2014
  • Add references to library conventions/rules in the standard itself; thanks to Beman for the suggestion!

    sdutoit committed May 23, 2012
  • Remove spurious paren

    sdutoit committed May 23, 2012
  • add implicitly generated special member functions bit based on suggestion from Beman

    sdutoit committed May 23, 2012