|
| From: | Akim Demaille |
| Subject: | Re: Index to appendices when --number |
| Date: | Mon, 24 Nov 2003 15:18:04 +0100 |
| User-agent: | Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) |
>> From: Akim Demaille <address@hidden>
>> Date: Mon, 24 Nov 2003 11:31:27 +0100
>>
>> I don't know whether the following difference bw sections and
>> appendices in the indices was meant:
> It's intentional: under --no-headers, if a section has a number, it is
> used, otherwise the name of the section is used.
> This policy might seem silly in a short document with a single chapter
> and a single appendix, with no sections or subsections, but it
> hopefully will make more sense in a real-life document.
> The reason that I decided to use "See 4.5" instead of "See ``Node''"
> is that in the plain-ASCII format it is much harder to find a section
> by its name than by its number.
Sorry, but I don't quite understand how this explains why appendices
and sections are treated differently. One of my documents looks like
the following. I'm not sure whether it looks nice :)
BTW, there are places where wrapping would look better.
A.4 Index
=========
### cheater: See 3.5.
### reevaluation: See 3.5.
*-tasks.hh and *-tasks.cc are impure: See 2.2.5.
--escapes-compute: See 4.5.
--escapes-display: See 4.5.
--types-check: See 4.6.2.
-T: See 4.6.2.
access.cc <1>: See 2.4.12.
access.cc: See 2.4.11.
access.hh <1>: See 2.4.12.
access.hh: See 2.4.11.
Accessors: See 2.2.6.
activation block:
See ``A.1 Glossary''.
aliasing: See 2.2.3.
ASM: See 4.11.
Assem: See 2.4.14.
assembly.hh: See 2.4.16.
AUTHORS: See 2.4.1.
Autoconf: See 5.3.
Automake: See 5.3.
basic block: See 4.8.2.2.
Bison: See 5.6.
Bjarne Stroustrup: See 5.2.
Boost.org: See 5.2.
build:
See ``A.1 Glossary''.
canonicalization: See 4.8.
Code duplication: See 2.2.3.
codegen-tasks.cc: See 2.4.16.
codegen-tasks.hh: See 2.4.16.
codegen.cc <1>: See 2.4.18.
codegen.cc: See 2.4.17.
codegen.hh <1>: See 2.4.18.
codegen.hh <2>: See 2.4.17.
codegen.hh: See 2.4.16.
color.hh: See 2.4.21.
common.hh: See 2.4.2.
commute: See 4.8.2.1.
Compilers: Principles, Techniques and Tools: See 5.2.
contract.hh: See 2.4.3.
Cool: The Classroom Object-Oriented Compiler: See 5.2.
cpu.hh: See 2.4.15.
curriculum:
See ``A.1 Glossary''.
Declarations in *.hh: See 2.2.5.
default-visitor.hh: See 2.4.6.
Definitions of functions and variables in *.cc: See 2.2.5.
depth_get: See 4.5.3.
Design Patterns: Elements of Reusable Object-Oriented Software: See 5.2.
distcheck: See 5.3.3.
dmalloc: See 5.5.
Dragon Book: See 5.2.
driver: See 2.4.2.
dynamic_cast: See 2.2.3.
Effective STL: See 5.2.
escape: See 2.4.3.
escape.hh: See 2.4.3.
escape_set: See 4.5.3.
escapes::EscapesVisitor: See 4.5.3.
EscapesVisitor: See 4.5.3.
ESN: See 5.2.
exp.hh: See 2.4.12.
FDL, GNU Free Documentation License:
See ``A.2 GNU Free Documentation License''.
Flex: See 5.6.
flow graph: See 4.10.
flowgraph.hh: See 2.4.20.
foo_get: See 2.2.6.
foo_set: See 2.2.6.
fragment.cc: See 2.4.14.
fragment.hh <1>: See 2.4.14.
fragment.hh: See 2.4.12.
frame.cc: See 2.4.11.
frame.hh: See 2.4.11.
gas-assembly.cc: See 2.4.18.
gas-assembly.hh: See 2.4.18.
gas-layout.cc: See 2.4.18.
gas-layout.hh: See 2.4.18.
GCC: See 5.4.
Generic Visitors in C++: See 5.2.
get: See 4.6.4.
GLIBCPP_FORCE_NEW: See 5.5.
GLIBCXX_FORCE_NEW: See 5.5.
GNU Build System: See 5.3.
GotW: See 5.2.
GotWN: See 5.2.
graph.hh: See 2.4.19.
graph.hxx: See 2.4.19.
Guru of the Week: See 5.2.
handler.hh: See 2.4.19.
handler.hxx: See 2.4.19.
HAVM <1>:
See ``A.1 Glossary''.
HAVM: See 5.7.
havm: See 4.7.2.1.
HIR: See 4.7.
host:
See ``A.1 Glossary''.
Hunt code duplication: See 2.2.3.
Hunt Leaks: See 2.2.3.
IA32:
See ``A.1 Glossary''.
ia32: See 2.4.16.
ia32-cpu.hh: See 2.4.15.
ia32-target.hh: See 2.4.15.
Inlined definitions in *.hxx: See 2.2.5.
INSTR: See 4.9.
instr.hh: See 2.4.14.
instruction selection: See 4.9.
interference-graph.cc: See 2.4.20.
interference-graph.hh: See 2.4.20.
iterator.hh: See 2.4.19.
iterator.hxx: See 2.4.19.
label.hh <1>: See 2.4.14.
label.hh: See 2.4.9.
layout.hh: See 2.4.14.
level-entry.hh: See 2.4.12.
level-env.hh: See 2.4.12.
level.cc: See 2.4.12.
level.hh: See 2.4.12.
Lex: See 5.6.
Lex & Yacc: See 5.2.
lib*.hh and lib*.cc are pure: See 2.2.5.
libassem.cc: See 2.4.14.
libassem.hh: See 2.4.14.
libcodegen.cc: See 2.4.16.
libcodegen.hh: See 2.4.16.
libparse.hh: See 2.4.7.
libregalloc.cc: See 2.4.21.
libregalloc.hh: See 2.4.21.
libtranslate.cc: See 2.4.12.
libtranslate.hh: See 2.4.12.
libtype.hh: See 2.4.8.
LIR: See 4.8.
liveness analysis: See 4.10.
liveness.cc: See 2.4.20.
liveness.hh: See 2.4.20.
location.hh <1>: See 2.4.7.
location.hh: See 2.4.6.
Make functor classes adaptable (ES40): See 2.2.4.
Making Compiler Design Relevant for Students who will (Most Likely) Never
Design a Compiler: See 5.2.
malloc: See 4.7.2.3.
mips: See 2.4.16.
mips-cpu.hh: See 2.4.15.
mips-target.hh: See 2.4.15.
Mipsy: See 5.8.
Modern C++ Design -- Generic Programming and Design Patterns Applied: See 5.2.
Modern Compiler Implementation in C, Java, ML: See 5.2.
move.hh: See 2.4.14.
Name private/protected members like_this_: See 2.2.3.
Name the parent class super_type: See 2.2.3.
Name your classes LikeThis: See 2.2.3.
Name your typedef FOO_type: See 2.2.3.
oper.hh: See 2.4.14.
Order class members by visibility first: See 2.2.6.
parsetiger.yy: See 2.4.7.
Parsing Techniques -- A Practical Guide: See 5.2.
patch: See 2.1.
Patches, applying: See 2.1.
Portland Pattern Repository: See 5.2.
position.hh <1>: See 2.4.7.
position.hh: See 2.4.6.
Prefer algorithm call to hand-written loops (ES43): See 2.2.4.
Prefer C Comments for Long Comments: See 2.2.6.
Prefer C++ Comments for One Line Comments: See 2.2.6.
Prefer Doxygen Documentation to plain comments: See 2.2.6.
Prefer dynamic_cast of references: See 2.2.3.
Prefer member functions to algorithms with the same names (ES44): See 2.2.4.
print: See 4.6.4.
print-visitor.hh: See 2.4.6.
put: See 4.6.4.
rebox: See 2.2.6.
regalloc-tasks.cc: See 2.4.21.
regalloc-tasks.hh: See 2.4.21.
regallocator.hh: See 2.4.21.
register allocation: See 4.11.
runtime, Tiger: See 2.4.16.
runtime.cc <1>: See 2.4.18.
runtime.cc: See 2.4.17.
runtime.s <1>: See 2.4.18.
runtime.s: See 2.4.17.
scantiger.ll: See 2.4.7.
scholarship:
See ``A.1 Glossary''.
schooling:
See ``A.1 Glossary''.
scope_begin: See 4.6.4.
scope_end: See 4.6.4.
sequence point: See 4.8.2.1.
set.hh: See 2.4.3.
snippet:
See ``A.1 Glossary''.
Specify comparison types for associative containers of pointers (ES20): See
2.2.4.
SPIM: See 5.9.
spim-assembly.cc: See 2.4.17.
spim-assembly.hh: See 2.4.17.
spim-layout.cc: See 2.4.17.
spim-layout.hh: See 2.4.17.
spot : une bibliothèque de vérification de propriétés de logique temporelle à
temps linéaire: See 5.2.
stack frame:
See ``A.1 Glossary''.
static hierarchy:
See ``A.1 Glossary''.
STL Home: See 5.2.
symbol.hh: See 2.4.5.
symbol::Table< class Entry_T >: See 4.6.4.
table.hh: See 2.4.5.
tarball name: See 5.3.1.
target:
See ``A.1 Glossary''.
target-tasks.cc: See 2.4.15.
target-tasks.hh: See 2.4.15.
target.hh: See 2.4.15.
tc: See 2.4.2.
tc.cc: See 2.4.2.
temp.hh: See 2.4.9.
test-flowgraph.cc: See 2.4.20.
test-graph.cc: See 2.4.19.
test-regalloc.cc: See 2.4.21.
The Design and Evolution of C++: See 5.2.
The Dragon Book: See 5.2.
Thinking in C++ Volume 1: See 5.2.
Thinking in C++ Volume 2: See 5.2.
tiger-runtime.c: See 2.4.16.
timer.cc: See 2.4.3.
timer.hh: See 2.4.3.
traces: See 4.8.2.2.
translate-visitor.hh: See 2.4.12.
translation.hh: See 2.4.12.
type checking: See 4.6.
type-entry.hh: See 2.4.8.
type-env.hh: See 2.4.8.
type::Error: See 4.6.5.
typeid: See 2.2.3.
types.hh: See 2.4.8.
Use \directive: See 2.2.6.
Use const references in arguments to save copies: See 2.2.3.
Use dynamic_cast for type cases: See 2.2.3.
Use foo_get, not get_foo: See 2.2.6.
Use pointers when passing an object together with its management: See 2.2.3.
Use rebox.el to markup paragraphs: See 2.2.6.
Use references for aliasing: See 2.2.3.
Use the Imperative: See 2.2.6.
Use virtual methods, not type cases: See 2.2.3.
Valgrind: See 5.5.
visitor.hh <1>: See 2.4.14.
visitor.hh: See 2.4.6.
vtable:
See ``A.1 Glossary''.
Write Documentation in Doxygen: See 2.2.6.
Writing Compilers and Interpreters -- An Applied Approach Using C++: See 5.2.
Yacc: See 5.6.
address@hidden: See 3.1.
| [Prev in Thread] | Current Thread | [Next in Thread] |