Merge pull request #1676 from wilzbach/add-labels-to-other

Add labels to spec

Author: CyberShadow

spec/arrays.dd

@@ -889,7 +889,7 @@ import std.stdio;
 writefln("the string is '%s'", str);
 ---------
 
-$(H3 Void Arrays)
+$(H3 $(LNAME2 void_arrays, Void Arrays))
 
     $(P There is a special type of array which acts as a wildcard that can hold
     arrays of any kind, declared as $(D void[]). Void arrays are used for

spec/class.dd

@@ -811,7 +811,7 @@ class Foo
 }
 ------
 
-$(H3 Shared Static Constructors)
+$(H3 $(LNAME2 shared_static_constructors, Shared Static Constructors))
 
 $(GRAMMAR
 $(GNAME SharedStaticConstructor):
@@ -823,7 +823,7 @@ $(GNAME SharedStaticConstructor):
         and are intended for initializing any shared global data.
         )
 
-$(H3 Shared Static Destructors)
+$(H3 $(LNAME2 shared_static_destructors, Shared Static Destructors))
 
 $(GRAMMAR
 $(GNAME SharedStaticDestructor):

spec/cpp_interface.dd

@@ -8,7 +8,7 @@ $(SPEC_S Interfacing to C++,
     through a $(DDLINK spec/interfaceToC, Interfacing to C, C interface) or a
     COM interface.)
 
-$(H2 The General Idea)
+$(H2 $(LNAME2 general_idea, The General Idea))
 
     $(P Being 100% compatible with C++ means more or less adding
     a fully functional C++ compiler front end to D.
@@ -45,7 +45,7 @@ $(H2 $(LNAME2 global-functions, Global Functions))
     $(P C++ global functions, including those in namespaces, can be declared
     and called in D, or defined in D and called in C++.)
 
-$(H3 Calling C++ Global Functions from D)
+$(H3 $(LNAME2 calling_cpp_global_from_d, Calling C++ Global Functions from D))
 
     $(P Given a C++ function in a C++ source file:)
 
@@ -113,7 +113,7 @@ k = 3
 
     )
 
-$(H3 Calling Global D Functions From C++)
+$(H3 $(LNAME2 calling_global_d_functions_from_cpp, Calling Global D Functions From C++))
 
     $(P To make a D function accessible from C++, give it
     C++ linkage:)
@@ -186,8 +186,8 @@ $(H2 $(LNAME2 classes, Classes))
     $(P Unlike classes and interfaces with D linkage, $(CODE extern (C++))
     classes and interfaces are not rooted in $(CODE Object) and cannot be used
     with $(CODE typeid).)
-    
-    $(P D structs and classes have different semantics whereas C++ structs and 
+
+    $(P D structs and classes have different semantics whereas C++ structs and
     classes are basically the same. The use of a D struct or class depends on
     the C++ implementation and not on the used C++ keyword.
     When mapping a D $(CODE class) onto a C++ $(CODE struct),
@@ -205,7 +205,7 @@ class Bar
 }
 ---
 
-$(H3 Using C++ Classes From D)
+$(H3 $(LNAME2 using_cpp_classes_from_d, Using C++ Classes From D))
 
     $(P The following example shows binding of a pure virtual function, its
     implementation in a derived class, a non-virtual member function, and a
@@ -315,7 +315,7 @@ instead disabled on the D side; an alternative would be to reimplement the
 constructor in D. See the $(DDSUBLINK spec/cpp_interface, lifetime-management,
 section below on lifetime management) for more information.)
 
-$(H3 Using D Classes From C++)
+$(H3 $(LNAME2 using_d_classes_from_cpp, Using D Classes From C++))
 
     $(P Given D code like:)
 
@@ -750,7 +750,7 @@ $(H2 $(LNAME2 exception-handling, Exception Handling))
     directly in C++ code (but they will be throwable indirectly by calling into
     a D function with C++ linkage).)
 
-$(SECTION2 Comparing D Immutable and Const with C++ Const,
+$(SECTION2 $(LNAME2 comparing-d-immutable-and-const-with-cpp-const, Comparing D Immutable and Const with C++ Const),
 
 $(TABLE_SPECIAL $(ARGS Const, Immutable Comparison),
     $(THEAD Feature, D, C++98)

spec/ddoc.dd

@@ -202,7 +202,7 @@ a line immediately followed by a ':'. This name forms the section name.
 The section name is not case sensitive.
 )
 
-$(H4 Summary)
+$(H4 $(LNAME2 summary, Summary))
 
 $(P
 The first section is the $(I Summary), and does not have a section name.
@@ -211,7 +211,7 @@ While the summary can be any length, try to keep it to one line.
 The $(I Summary) section is optional.
 )
 
-$(H4 Description)
+$(H4 $(LNAME2 description, Description))
 
 $(P
 The next unnamed section is the $(I Description).
@@ -446,17 +446,17 @@ $(DD The syntax is $(B /c/string/), where $(B c)
 ------------------------------------
 )
 
-$(H2 Highlighting)
+$(H2 $(LNAME2 highlighting, Highlighting))
 
-$(H4 Embedded Comments)
+$(H4 $(LNAME2 embedded_comments, Embedded Comments))
 
 $(P
     The documentation comments can themselves be commented using
     the $(DOLLAR)$(D (DDOC_COMMENT comment text)) syntax. These comments do not
     nest.
 )
 
-$(H4 Embedded Code)
+$(H4 $(LNAME2 embedded_code, Embedded Code))
 
 $(P
     D code can be embedded using lines beginning with at least three
@@ -485,7 +485,7 @@ $(P
     so that $(D_COMMENT /* ... */) can be used inside the code section.
 )
 
-$(H4 Inline Code)
+$(H4 $(LNAME2 inline_code, Inline Code))
 
 $(P
     Inline code can be written between backtick characters ($(BACKTICK)), similarly
@@ -514,7 +514,7 @@ $(P
  void bar() {}
 ---
 
-$(H4 Embedded HTML)
+$(H4 $(LNAME2 embedded_html, Embedded HTML))
 
 $(P
 HTML can be embedded into the documentation comments, and it will
@@ -535,7 +535,7 @@ best to avoid using it where practical.
  */
 ------------------------------------
 
-$(H4 Emphasis)
+$(H4 $(LNAME2 emphasis, Emphasis))
 
 $(P
 Identifiers in documentation comments that are function parameters or are
@@ -548,7 +548,7 @@ To prevent unintended emphasis of an identifier, it can be preceded by
 an underscore ($(UNDERSCORE)). The underscore will be stripped from the output.
 )
 
-$(H4 Character Entities)
+$(H4 $(LNAME2 character_entities, Character Entities))
 
 $(P
     Some characters have special meaning
@@ -567,7 +567,7 @@ $(P
     special character is not immediately followed by a $(HASH) or a letter.
 )
 
-$(H4 No Documentation)
+$(H4 $(LNAME2 no_documentation, No Documentation))
 
 $(P
     No documentation is generated for the following constructs,
@@ -582,7 +582,7 @@ $(P
     $(LI Class info, type info, and module info)
     )
 
-$(H2 Macros)
+$(H2 $(LNAME2 macros, Macros))
 
 $(P
     The documentation comment processor includes a simple macro
@@ -979,7 +979,7 @@ $(H3 $(LNAME2 macro_def_ddocgenerated, Macro Definitions Generated by Ddoc))
     )
     )
 
-$(H2 Using Ddoc to generate examples from unit tests)
+$(H2 $(LNAME2 using_ddoc_to_generate_examples, Using Ddoc to generate examples from unit tests))
 
 $(P
     Ddoc can automatically generate usage examples for declarations
@@ -1005,7 +1005,7 @@ unittest
     $(DPLLINK unittest.html#documented-unittests, documented unit tests).
 )
 
-$(H2 Using Ddoc for other Documentation)
+$(H2 $(LNAME2 using_ddoc_for_other_documentation, Using Ddoc for other Documentation))
 
 $(P
     Ddoc is primarily designed for use in producing documentation
@@ -1043,7 +1043,7 @@ $(P
     cross-site scripting).
 )
 
-$(H2 Links to D documentation generators)
+$(H2 $(LNAME2 links_to_d_documentation_generators, Links to D documentation generators))
 
 $(P
     A list of current D documentation generators which use Ddoc

spec/iasm.dd

@@ -187,7 +187,7 @@ $(GNAME Register64):
     $(D YMM8) $(D YMM9) $(D YMM10) $(D YMM11) $(D YMM12) $(D YMM13) $(D YMM14) $(D YMM15)
 )
 
-$(H3 Special Cases)
+$(H3 $(LNAME2 special_cases, Special Cases))
 
 $(DL
     $(DT $(D lock), $(D rep), $(D repe), $(D repne), $(D repnz), $(D repz))
@@ -1072,7 +1072,7 @@ $(H3 $(LNAME2 simd, SIMD))
     $(P SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2 and AVX are supported.)
 
 $(COMMENT
-$(H3 Other)
+$(H3 $(LNAME2 other, Other))
     $(P AES, CMUL, FSGSBASE, RDRAND, FP16C and FMA are supported.)
 )
 

spec/memory-safe-d.dd

@@ -21,7 +21,7 @@ $(SPEC_S Memory Safety,
 		)
 	)
 
-$(H3 Usage)
+$(H3 $(LNAME2 usage, Usage))
 
 	$(P Memory safety can be enabled on a per-function basis using
 	the $(DDSUBLINK spec/function, safe-functions, $(D @safe) attribute).
@@ -36,7 +36,7 @@ $(H3 Usage)
 	-release) mode.
 	)
 
-$(H3 Limitations)
+$(H3 $(LNAME2 limitations, Limitations))
 
 	$(P Memory safety does not imply that code is portable, uses only
 	sound programming practices, is free of byte order dependencies,

spec/operatoroverloading.dd

@@ -85,7 +85,7 @@ int foo(S s)
 }
 ---
 
-$(H3 Postincrement $(I e)$(D ++) and Postdecrement $(I e)$(D --) Operators)
+$(H3 $(LNAME2 postincrement_postdecrement_operators, Postincrement $(I e)$(D ++) and Postdecrement $(I e)$(D --) Operators))
 
 	$(P These are not directly overloadable, but instead are rewritten
 	in terms of the ++$(I e) and --$(I e) prefix operators:
@@ -101,7 +101,7 @@ $(H3 Postincrement $(I e)$(D ++) and Postdecrement $(I e)$(D --) Operators)
 	$(ARGS $(D $(LPAREN)auto t =) $(I e)$(D , ++)$(I e)$(D , t$(RPAREN))))
 	)
 
-$(H3 Overloading Index Unary Operators)
+$(H3 $(LNAME2 index_unary_operators, Overloading Index Unary Operators))
 
 	$(TABLE2 Overloadable Index Unary Operators,
 	$(THEAD $(I op), $(I rewrite))
@@ -130,7 +130,7 @@ $(H3 Overloading Index Unary Operators)
 	)
 	)
 
-$(H3 Overloading Slice Unary Operators)
+$(H3 $(LNAME2 slice_unary_operators, Overloading Slice Unary Operators))
 
 	$(TABLE2 Overloadable Slice Unary Operators,
 	$(THEAD $(I op), $(I rewrite))
@@ -202,7 +202,7 @@ $(H3 Overloading Slice Unary Operators)
 
 $(H2 $(LEGACY_LNAME2 Cast, cast, Cast Operator Overloading))
 
-    $(P To define how one type can be cast to another, define the 
+    $(P To define how one type can be cast to another, define the
       `opCast` template method, which is used as follows:)
 	$(TABLE2 Cast Operators,
 	$(THEAD $(I op), $(I rewrite))
@@ -216,7 +216,7 @@ $(H2 $(LEGACY_LNAME2 Cast, cast, Cast Operator Overloading))
         expression, except in the case of boolean operations (see next
         section))
 
-$(H3 Boolean Operations)
+$(H3 $(LNAME2 boolean_operators, Boolean Operations))
 
 	$(P Notably absent from the list of overloaded unary operators is the !
 	logical negation operator. More obscurely absent is a unary operator
@@ -571,7 +571,7 @@ $(H2 $(LEGACY_LNAME2 Assignment, assignment, Assignment Operator Overloading))
     c = 1;        // Rewritten to c.opAssign(1);
     ---
 
-$(H3 Index Assignment Operator Overloading)
+$(H3 $(LNAME2 index_assignment_operator, Index Assignment Operator Overloading))
 
 	$(P If the left hand side of an assignment is an index operation
 	on a struct or class instance,
@@ -593,7 +593,7 @@ void test()
 }
 -------
 
-$(H3 Slice Assignment Operator Overloading)
+$(H3 $(LNAME2 slice_assignment_operator, Slice Assignment Operator Overloading))
 
 	$(P If the left hand side of an assignment is a slice operation on a
 	struct or class instance, it can be overloaded by implementing an $(D
@@ -653,7 +653,7 @@ a $(METACODE op)= b
 a.opOpAssign!($(DOUBLEQUOTE $(METACODE op)))(b)
 ---
 
-$(H3 Index Op Assignment Operator Overloading)
+$(H3 $(LNAME2 index_op_assignment, Index Op Assignment Operator Overloading))
 
 	$(P If the left hand side of an $(I op)= is an index expression on
 	a struct or class instance and $(D opIndexOpAssign) is a member:)
@@ -668,7 +668,7 @@ a[$(METACODE $(ARGUMENTS))] $(METACODE op)= c
 a.opIndexOpAssign!($(DOUBLEQUOTE $(METACODE op)))(c, $(METACODE $(ARGUMENTS)))
 ---
 
-$(H3 Slice Op Assignment Operator Overloading)
+$(H3 $(LNAME2 slice_op_assignment, Slice Op Assignment Operator Overloading))
 
 	$(P If the left hand side of an $(I op)= is a slice expression on
 	a struct or class instance and $(D opIndexOpAssign) is a member:)

spec/pragma.dd

@@ -158,7 +158,7 @@ pragma(startaddress, foo);
     )
     )
 
-$(H3 Vendor Specific Pragmas)
+$(H3 $(LNAME2 vendor_specific_pragmas, Vendor Specific Pragmas))
 
         $(P Vendor specific pragma $(I Identifier)s can be defined if they
         are prefixed by the vendor's trademarked name, in a similar manner

spec/property.dd

@@ -65,7 +65,7 @@ $(THEAD Property, Description)
 $(TROW $(RELATIVE_LINK2 classinfo, $(D .classinfo)), Information about the dynamic type of the class)
 )
 
-$(SECTION3 $(LNAME2 init, .init) Property,
+$(SECTION3 $(LNAME2 init, .init Property),
 
 	$(P $(D .init) produces a constant expression that is the default
 	initializer. If applied to a type, it is the default initializer
@@ -144,7 +144,7 @@ void main()
     )
 )
 
-$(SECTION3 $(LNAME2 stringof, .stringof) Property,
+$(SECTION3 $(LNAME2 stringof, .stringof Property),
 
 	$(P $(D .stringof) produces a constant string that is the
 	source representation of its prefix.
@@ -226,7 +226,7 @@ $(SECTION3 $(LNAME2 alignof, .alignof Property),
 	)
 )
 
-$(SECTION3 $(LNAME2 classinfo, .classinfo) Property,
+$(SECTION3 $(LNAME2 classinfo, .classinfo Property),
 
 	$(P $(CODE .classinfo) provides information about the dynamic type
 	of a class object.

spec/struct.dd

@@ -289,7 +289,7 @@ $(TROW $(D .sizeof), Size in bytes of struct)
 $(TROW $(D .alignof), Size boundary struct needs to be aligned on)
 $(TROW $(D .tupleof), Gets type tuple of fields))
 
-$(H3 Struct Field Properties)
+$(H3 $(LNAME2 struct_field_properties, Struct Field Properties))
 
 $(TABLE2 Struct Field Properties,
 $(THEAD Name, Description)