Merge pull request #2174 from wilzbach/articles

Move articles pages to /articles

Author: wilzbach

.htaccess

@@ -67,5 +67,26 @@ Redirect 301 /sponsors.html https://dlang.org/foundation/sponsors.html
 Redirect 301 /dlangupb-scholarship.html https://dlang.org/foundation/updscholarship.html
 Redirect 301 /donate.html https://dlang.org/foundation/donate.html
 
+# Legacy article pages
+Redirect 301 /ctod.html /articles/ctod.html
+Redirect 301 /cpptod.html /articles/cpptod.html
+Redirect 301 /pretod.html /articles/pretod.html
+Redirect 301 /code_coverage.html /articles/code_coverage.html
+Redirect 301 /exception-safe.html /articles/exception-safe.html
+Redirect 301 /hijack.html /articles/hijack.html
+Redirect 301 /intro-to-datetime.html /articles/intro-to-datetime.html
+Redirect 301 /lazy-evaluation.html /articles/lazy-evaluation.html
+Redirect 301 /migrate-to-shared.html /articles/migrate-to-shared.html
+Redirect 301 /mixin.html /articles/mixin.html
+Redirect 301 /regular-expression.html /articles/regular-expression.html
+Redirect 301 /safed.html /articles/safed.html
+Redirect 301 /templates-revisited.html /articles/templates-revisited.html
+Redirect 301 /ctarguments.html /articles/ctarguments.html
+Redirect 301 /variadic-function-templates.html /articles/variadic-function-templates.html
+Redirect 301 /d-array-article.html /articles/d-array-article.html
+Redirect 301 /cppcontracts.html /articles/cppcontracts.html
+Redirect 301 /template-comparison.html /articles/template-comparison.html
+Redirect 301 /dll-linux.html /articles/dll-linux.html
+
 # Error pages
 ErrorDocument 404 /404.html

articles/articles.ddoc

@@ -0,0 +1 @@
+ROOT_DIR = ../

builtin.dd renamed to articles/builtin.dd

@@ -2,6 +2,8 @@ Ddoc
 
 $(COMMUNITY D's Contract Programming vs C++'s,
 
+$(HEADERNAV_TOC)
+
         $(P Many people have written me saying that D's Contract Programming
         does not add anything that C++ does not already support.
         They go on to illustrate their point with a technique for doing Contracts in
@@ -16,7 +18,7 @@ $(COMMUNITY D's Contract Programming vs C++'s,
         to support Contracts, but they are not covered here because they are not
         part of standard C++ and are not supported by any other C++ compiler.)
 
-$(H2 Contract Programming in D)
+$(H2 $(LNAME2 contract-programming-d, Contract Programming in D))
 
         This is more fully documented in the D
         <a href="contracts.html">Contract Programming</a> document.
@@ -64,9 +66,9 @@ $(H2 Contract Programming in D)
 
         )
 
-$(H2 Contract Programming in C++)
+$(H2 $(LNAME2 contract-progamming-cpp, Contract Programming in C++))
 
-$(H3 The $(D assert) Macro)
+$(H3 $(LNAME2 assert-macro, The $(D assert) Macro))
 
         $(P C++ does have the basic $(D assert) macro, which tests its argument
         and if it fails, aborts the program. $(D assert) can be turned
@@ -80,7 +82,7 @@ $(H3 The $(D assert) Macro)
         $(P $(D assert) is where explicit support for Contracts in Standard C++
         begins and ends.)
 
-$(H3 Class Invariants)
+$(H3 $(LNAME2 class-invariant, Class Invariants))
 
         Consider a class invariant in D:
 
@@ -215,7 +217,7 @@ int A::foo()
         The #if DBC is still there because some compilers may not
         optimize the whole thing away if check_invariants compiles to nothing.
 
-$(H2 Preconditions and Postconditions)
+$(H3 Preconditions and Postconditions)
 
         Consider the following in D:
 
@@ -366,7 +368,7 @@ int foo(int a, int b)
 }
 )
 
-$(H2 Preconditions and Postconditions for Member Functions)
+$(H3 $(LNAME2 pre-post-conditions, Preconditions and Postconditions for Member Functions))
 
         Consider the use of preconditions and postconditions for a
         polymorphic function in D:
@@ -464,7 +466,7 @@ public:
         and parameters
         for $(D foo()).
 
-$(H2 Conclusion)
+$(H2 $(LNAME2 conclusion, Conclusion))
 
         $(P These C++ techniques can work up to a point. But, aside from
         $(D assert), they are not standardized and so will vary from
@@ -476,7 +478,7 @@ $(H2 Conclusion)
         way to use Contracts and get it right. Being in the language standardizes
         the way it will be used from project to project.)
 
-$(H2 References)
+$(H2 $(LNAME2 references, References))
 
         $(P Chapter C.11 introduces the theory and rationale of
         Contract Programming in
@@ -495,5 +497,6 @@ $(H2 References)
 
 Macros:
         TITLE=D's Contract Programming vs C++'s
+        SUBNAV=$(SUBNAV_ARTICLES)