From: Jonathan Wakely Date: Wed, 21 May 2003 12:15:18 +0000 (+0100) Subject: test.html: Fix markup. X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=baf64b4ec1f4b3cc09740fe06cb69904d04acb0c;p=platform%2Fupstream%2Fgcc.git test.html: Fix markup. 2003-05-21 Jonathan Wakely * docs/html/test.html: Fix markup. From-SVN: r67060 --- diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 8ff83f7..da29c21 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,7 @@ +2003-05-21 Jonathan Wakely + + * docs/html/test.html: Fix markup. + 2003-05-21 Danny Smith * libmath/stubs.c (hypot, hypotf, hypotl): Don't divide by diff --git a/libstdc++-v3/docs/html/test.html b/libstdc++-v3/docs/html/test.html index 61e3725..42d7d76 100644 --- a/libstdc++-v3/docs/html/test.html +++ b/libstdc++-v3/docs/html/test.html @@ -50,7 +50,7 @@ the C++ standard, and each containing test files or subdirectories of test files that test for that particular part of the standard. -

+ 

 17_intro
@@ -97,7 +97,7 @@ data		  Sample text files for testing input and output.
       was named accordingly. For instance, to test items related to
        21.3.6.1 - basic_string::find [lib.string::find]
       in the standard, the following was used:
-   

+   

    
 21_strings/find.cc
    
   
@@ -142,11 +142,11 @@ data		  Sample text files for testing input and output.
       This test case expects some kind of interactive input in order
       to finish or pass. At the moment, the interactive tests are not
       run by default. Instead, they are run by hand, like:
+   

       
 
 g++ 27_io/objects/char/3_xin.cc
 cat 27_io/objects/char/3_xin.in | a.out
      
 
-   

 
 
  • 
    .in
@@ -320,17 +320,17 @@ cat 27_io/objects/char/3_xin.in | a.out
 #	compile).
 #
 # dg-error regexp comment [{ target/xfail selector } [{.|0|linenum}]]
-#	indicate an error message  is expected on this line
+#	indicate an error message <regexp> is expected on this line
 #	(the test fails if it doesn't occur)
 #	Linenum=0 for general tool messages (eg: -V arg missing).
 #	"." means the current line.
 #
 # dg-warning regexp comment [{ target/xfail selector } [{.|0|linenum}]]
-#	indicate a warning message  is expected on this line
+#	indicate a warning message <regexp> is expected on this line
 #	(the test fails if it doesn't occur)
 #
 # dg-bogus regexp comment [{ target/xfail selector } [{.|0|linenum}]]
-#	indicate a bogus error message  use to occur here
+#	indicate a bogus error message <regexp> use to occur here
 #	(the test fails if it does occur)
 #
 # dg-build regexp comment [{ target/xfail selector }]
@@ -344,7 +344,7 @@ cat 27_io/objects/char/3_xin.in | a.out
 #	(this should only be used sparingly and temporarily)
 #
 # dg-output regexp [{ target selector }]
-#	indicate the expected output of the program is 
+#	indicate the expected output of the program is <regexp>
 #	(there may be multiple occurrences of this, they are concatenated)
 #
 # dg-final { tcl code }
@@ -394,11 +394,11 @@ Example 4: Testing for compilation errors on line 41
 
    
    You can check the status of the build without installing it
    using the dejagnu harness, much like the rest of the gcc tools.
    
-   
    
-   
     make check
     in the libbuilddir directory.
    
+   
     make check
    
+   
    in the libbuilddir directory.
    
    
    or
    
-   
     make check-target-libstdc++-v3
     in the
-   gccbuilddir directory.
    
+   
     make check-target-libstdc++-v3
    
+   
    in the gccbuilddir directory.
    
 
    
    
       These commands are equivalent and will create a 'testsuite'
@@ -476,7 +476,7 @@ make check-target-libstdc++-v3 RUNTESTFLAGS="--target_board=arm-sim"
    
     In addition, there are some testing options that are mostly of
    interest to library maintainers and system integrators. As such,
    these tests may not work on all cpu and host combinations, and must
-   be executed in the libbuilddir directory.
     These options
+   be executed in the libbuilddir directory.  These options
    include, but are not necessarily limited to, the following:
    
    
 
@@ -530,25 +530,38 @@ Diffing of expected output to standard streams needs to be finished off.
 
    
 The V3 testing framework supports, or will eventually support,
 additional keywords for the purpose of easing the job of writing
-test cases.  All V3-keywords are of the form @xxx@.  Currently plans
-for supported keywords include:
+test cases.  All V3-keywords are of the form @xxx@.
+Currently plans for supported keywords include:
 
    
 
-  @require@ 
-      The existence of  is essential for the test to complete
+
    
+
      @require@ <files>  
    
+
    
+   
    
+      The existence of <files> is essential for the test to complete
       successfully.  For example, a test case foo.C using bar.baz as
       input file could say
-	    // @require@ bar.baz
+   
    
+   
    +	    // @require@ bar.baz
    
+   
    
       The special variable % stands for the rootname, e.g. the
       file-name without its `.C' extension.  Example of use (taken
       verbatim from 27_io/filebuf.cc)
-	   // @require@ %-*.tst %-*.txt
-
-  @diff@  
+   
    
+   
    +	   // @require@ %-*.tst %-*.txt
    
+
    
+
      @diff@ <first-list> <second-list>  
    
+
    
+   
    
       After the test case compiles and ran successfully, diff
-       against , these lists should have the
-      same length.  The test fails if diff returns non-zero a pair of
-      files.
+      <first-list> against <second-list>, these lists should
+      have the same length.  The test fails if diff returns non-zero a
+      pair of files.
+   
    
+
    
+