Change /(3.8)/(v3.8)/

Author: Arnd R. Strube

manual.markdown

@@ -246,8 +246,8 @@ The test execution of this will *likely* (no guarantee of order in CppUTest) be:
 * *-sg group* only run test whose group exactly matches the string *group*
 * *-sn name* only run test whose name exactly matches the string *name*
 * *-v* verbose, print each test name as it runs
-* *-xg group* exclude tests whose group contains the substring *group* (3.8)
-* *-xn name* exclude tests whose name contains the substring *name* (3.8)
+* *-xg group* exclude tests whose group contains the substring *group* (v3.8)
+* *-xn name* exclude tests whose name contains the substring *name* (v3.8)
 * *"TEST(group, name)"* only run test whose group and name matches the strings group and name. This can be used to copy-paste output from the -v option on the command line.
 
 You can specify multiple -s|sg, -s|sn and "TEST(group, name)" parameters: 
@@ -391,7 +391,7 @@ Test plugins let you add a pre-action and a post-action to each test case.  Plug
 
 * Memory leak detector (provided)
 * Pointer restore mechanism (provided) - helpful when tests overwrite a pointer that must be restored to its original value after the test.  This is especially helpful when a pointer to a function is modified for test purposes.
-* IEEE754 Floating point exceptions (provided; 3.8) - automatically checks whether any floating point exception flags are set at the end of every test and if so, fails the test.
+* IEEE754 Floating point exceptions (provided; v3.8) - automatically checks whether any floating point exception flags are set at the end of every test and if so, fails the test.
 * All Mutex's released - you could write a plugin that checks that any Mutexs or other shared resource is released before the test exits.
 
 Complete Documentation for provided plugins can be found on the [Plugins Manual](plugins_manual.html) page.

mocking_manual.markdown

@@ -299,7 +299,7 @@ mock().expectOneCall("Foo").withOutputParameterReturning("bar", &doubleOutputVal
 
 ### Output Parameters Using Objects
 
-By far the best way to handle output parameters is by using a custom type copier (3.8). The general principle is similar to the custom comparators described above:
+By far the best way to handle output parameters is by using a custom type copier (v3.8). The general principle is similar to the custom comparators described above:
 
 {% highlight c++ %}
 MyType outputValue = 4;
@@ -532,14 +532,14 @@ mock_c()->clear();
 
 The C interface uses a similar builder structure as the C++ interface. It is far less common in C, but it works the same.
 
-It is now also possible to specify the actual return value in the same way as with C++ (3.8):
+It is now also possible to specify the actual return value in the same way as with C++ (v3.8):
 
 {% highlight c++ %}
 return mock_c()->actualCall("foo")->withIntParameters("integer", 10)->doubleReturnValue();
 return mock_c()->doubleReturnValue();
 {% endhighlight %}
 
-and to specify a default return value, in case mocking is currently disabled when the actual call occurs (3.8):
+and to specify a default return value, in case mocking is currently disabled when the actual call occurs (v3.8):
 
 {% highlight c++ %}
 return mock_c()->actualCall("foo")->withIntParameters("integer", 10)->returnDoubleValueOrDefault(2.25);

plugin_manual.markdown

@@ -120,12 +120,12 @@ This plugin detects floating point error conditions and fails the test, if any w
 This is a list of floating point error conditions, and how they are supported by the plugin:
 
 {% highlight c++ %}
-FE_DIVBYZERO   /* supported (3.8) */
-FE_OVERFLOW    /* supported (3.8) */
-FE_UNDERFLOW   /* supported (3.8) */
-FE_INVALID     /* supported (3.8) */
-FE_INEXACT     /* supported; disabled by default (3.8) */
-FE_DENORMAL    /* NOT supported (3.8) */
+FE_DIVBYZERO   /* supported (v3.8) */
+FE_OVERFLOW    /* supported (v3.8) */
+FE_UNDERFLOW   /* supported (v3.8) */
+FE_INVALID     /* supported (v3.8) */
+FE_INEXACT     /* supported; disabled by default (v3.8) */
+FE_DENORMAL    /* NOT supported (v3.8) */
 {% endhighlight %}
 
 You can turn on FE_INEXACT checking manually, although this probably won't be very useful most of the time, since almost every floating-point operation is likely to set this flag: