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

Dangling references in index #5051

Closed
timsong-cpp opened this issue Oct 21, 2021 · 2 comments · Fixed by #5066
Closed

Dangling references in index #5051

timsong-cpp opened this issue Oct 21, 2021 · 2 comments · Fixed by #5066
Assignees

Comments

@timsong-cpp
Copy link
Contributor

The following see entries have no matching target:

draft/source/overloading.tex

Lines 3349 to 3350 in 3a9f398

\indextext{increment operator!overloaded|see{overloading, increment operator}}%
\indextext{decrement operator!overloaded|see{overloading, decrement operator}}%

draft/source/lex.tex

Lines 22 to 23 in 3a9f398

\indextext{null character|see{character, null}}
\indextext{null wide character|see{wide-character, null}}

\indextext{\idxcode{0}!null character|see {character, null}}%

draft/source/numerics.tex

Lines 10186 to 10187 in 3a9f398

\indextext{Eulerian integral of the first kind|see{\tcode{beta}}}%
\indextext{beta functions $\mathsf{B}$}%

The last one is kind of special - it points to beta, which is not in the main index (it's in the index of library names). It's probably better to point to beta functions $\mathsf{B}$ index instead.

@jensmaurer
Copy link
Member

@timsong-cpp , we ought to augment our automated machinery to detect these. How did you find them?

@timsong-cpp
Copy link
Contributor Author

Grepping the HTML index produced by cxxdraft-htmlgen to find the target of each see and then grepping each to figure out if they exist in the HTML. I don't know if it's possible to do it just from the LaTeX build products.

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 a pull request may close this issue.

2 participants