s/(possibly cv-qualified)/\\cv{}~/ and allied changes. #1142
Conversation
|
@jensmaurer: Could you please take a look? Weren't you working in that field recently? |
| @@ -401,7 +401,7 @@ | |||
| type \tcode{T} (Clause~\ref{conv}, \ref{expr.type.conv}, | |||
| \ref{expr.dynamic.cast}, \ref{expr.static.cast}, \ref{expr.cast}), or | |||
| \item an expression that is not a null pointer constant, and has type | |||
| other than \cv{} \tcode{void*}, is converted to the type pointer to \tcode{T} | |||
| other than \cv{}~\tcode{void*}, is converted to the type pointer to \tcode{T} | |||
| or reference to \tcode{T} using a standard conversion | |||
There was a problem hiding this comment.
In general (not a comment on this change), instead of "cv void *", I'd like to see phrasing such as "pointer to cv void" (in double quotes). The latter is the "official" type language introduced in 8.3, and we should use it, in particular when we do not-quite-C++ things such as \cv with it.
|
This looks good to me, i.e. this patch does what the description above says. The bulk of the changes is adding non-breaking spaces between \cv{} and the stuff that follows; this has the chance of introducing more overfull/underfull hboxes, but we can fix those later. It would be good to get this in sooner rather than later, because the changes overlap with the changes planned for #1139. @zygoloid: Please merge this after confirming the general plan is ok. |
|
Rebased. Anything else for me to do? |
|
Ping. |
As previously discussed with the Project Editor, changed (mainly in <type_traits> tables but also in other places) occurrences of "(possibly cv-qualified)" followed by a type (usually void, but also occasionally bool, etc.) by the \cv{} macro. To avoid a line break after \cv{}, replaced the space by a tilde (i.e., by a non-breaking space).