[PATCH] D45406: Document -std= values for different languages

This revision was automatically updated to reflect the committed changes. Closed by commit rL329827: Document -std= values for different languages (authored by dim, committed by ). Herald added a subscriber: llvm-commits. Changed prior to commit:

[PATCH] D45406: Document -std= values for different languages

rsmith accepted this revision. rsmith added a comment. This revision is now accepted and ready to land. Looks good to me, thank you Repository: rC Clang https://reviews.llvm.org/D45406 ___ cfe-commits mailing list cfe-commits@lists.llvm.org

[PATCH] D45406: Document -std= values for different languages

dim added a comment. Ping Repository: rC Clang https://reviews.llvm.org/D45406 ___ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[PATCH] D45406: Document -std= values for different languages

dim added a comment. So, does this look good enough to commit? Repository: rC Clang https://reviews.llvm.org/D45406 ___ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

[PATCH] D45406: Document -std= values for different languages

dim updated this revision to Diff 141529. dim added a comment. Attempt to put the standard values in to definition lists. In the HTML output, this looks fairly nice, but as a man page, it seems a bit strange, for example: -std= Specify the language standard to compile for.

[PATCH] D45406: Document -std= values for different languages

mgorny added a comment. I think you'd want a definition list instead then. But I haven't tested if they can be nested inside option lists. Repository: rC Clang https://reviews.llvm.org/D45406

[PATCH] D45406: Document -std= values for different languages

dim added a comment. In https://reviews.llvm.org/D45406#1060914, @mgorny wrote: > Well, my idea was to list the standards one per line (like on GCC manpage), > and then the '(deprecated)' comments would probably stand out enough to apply > to a single line. Also, FWICS the gcc manpage simply

[PATCH] D45406: Document -std= values for different languages

mgorny added a comment. Well, my idea was to list the standards one per line (like on GCC manpage), and then the '(deprecated)' comments would probably stand out enough to apply to a single line. Also, FWICS the gcc manpage simply lists which aliases are deprecated in the description text. But

[PATCH] D45406: Document -std= values for different languages

dim updated this revision to Diff 141513. dim added a comment. - Use "values" instead of "options" - Remove deprecated standard values Repository: rC Clang https://reviews.llvm.org/D45406 Files: docs/CommandGuide/clang.rst Index: docs/CommandGuide/clang.rst

[PATCH] D45406: Document -std= values for different languages

rsmith added a comment. In https://reviews.llvm.org/D45406#1060773, @dim wrote: > In https://reviews.llvm.org/D45406#1060768, @mgorny wrote: > > > To be honest, I find those '(deprecated)' confusing — the user may > > mistakenly assume that it's about all values rather than the alias. > > >

[PATCH] D45406: Document -std= values for different languages

dim added a comment. In https://reviews.llvm.org/D45406#1060768, @mgorny wrote: > To be honest, I find those '(deprecated)' confusing — the user may mistakenly > assume that it's about all values rather than the alias. Sure, what would you suggest as an alternative? Not listing them, listing

[PATCH] D45406: Document -std= values for different languages

mgorny added a comment. To be honest, I find those '(deprecated)' confusing — the user may mistakenly assume that it's about all values rather than the alias. Comment at: docs/CommandGuide/clang.rst:105 + + Supported options for the C language are: +

[PATCH] D45406: Document -std= values for different languages

dim created this revision. dim added reviewers: rsmith, dexonsmith, sylvestre.ledru, mgorny. Herald added subscribers: krytarowski, fhahn. After a remark on a FreeBSD mailing list that the clang man page did not have any list of possible values for the `-std=` flag, I have now attempted to