Skip to content
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

[macros,class] Define \defnadj and use it experimentally #2080

Merged
merged 1 commit into from Jul 6, 2018

Conversation

jensmaurer
Copy link
Member

Partially addresses #2067.

@jensmaurer
Copy link
Member Author

This is the trial balloon; if we agree on this approach, a full-scale cleanup is required.

@jensmaurer
Copy link
Member Author

Rebased.

@zygoloid
Copy link
Member

What is the c short for? Maybe \defnadj{foo}{bar} (as in, this is a definition of the adjective "foo" when applied to "bar"s) would be a be better mnemonic device?

@jensmaurer
Copy link
Member Author

"c" stands for "see", because this form of \defn adds a "see" entry. We might use this form also for non-adjective cases, e.g. \defnc{horse}{doctor} (adds "horse doctor, see doctor, horse").

@zygoloid
Copy link
Member

zygoloid commented Jul 2, 2018

Hmm, would it really be appropriate to use the same macro for both of those cases? I could imagine we might choose one day to italicize (or, say, hyperlink) only the "trivial" in "A \defnc{trivial}{class} is [...]", whereas we'd want to italicize both words in "A \defnc{horse}{doctor} is [...]". The two seem semantically different, so using different markup may be best.

In the ISO Terms and Definitions sense, the former case is

trivial
<class> trivially-copyable with a trivial default constructor

whereas the latter is

horse doctor
doctor specializing in horses

@tkoeppe
Copy link
Contributor

tkoeppe commented Jul 2, 2018 via email

@jensmaurer
Copy link
Member Author

@zygoloid: Adjusted to \defnadj.

@jensmaurer jensmaurer changed the title [macros,class] Define \defnc and use it experimentally [macros,class] Define \defnadj and use it experimentally Jul 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants