Parameter library Workarounds for Borland and MSVC

Parameter library explicit markup for expected failures

value_init.hpp:
  Borland workarounds
  Use angle-includes consistently


[SVN r35084]

libs/parameter

@@ -1 +1 @@
-Subproject commit 28f98ecbf0d30ea2aa9c476634fa3b14c89efdb9
+Subproject commit b9f287ea527bf99fe8d87453030868bc5cae7542

libs/utility

@@ -1 +1 @@
-Subproject commit e55610a0d08ea0567225d36dfb9a5ec6ee988394
+Subproject commit c730ab4ffb2b465c7bd288b4768d8752b7c48aa5

status/explicit-failures-markup.xml

@@ -2980,6 +2980,22 @@ for more information.
 
     </library>
 
+    <!-- parameter -->
+    <library name="parameter">
+        <mark-expected-failures>
+            <test name="duplicates"/>
+            <toolset name="borland-5.6*"/>
+            <toolset name="borland-5.8*"/>
+            <note refid="32"/>
+        </mark-expected-failures>
+        <mark-expected-failures>
+            <test name="unnamed_fail"/>
+            <toolset name="msvc-7.0"/>
+            <toolset name="msvc-6.0"/>
+            <note refid="32"/>
+        </mark-expected-failures>
+    </library>
+
      <!-- pointer container -->
     <library name="ptr_container">
         <mark-unusable>
@@ -4720,7 +4736,7 @@ for more information.
     </note>
 
     <note id="1">
-        The failure is caused by a problem in Boost code. The Boost developers is aware of
+        The failure is caused by a problem in Boost code. The Boost developers are aware of
         the problem and plan to fix it.
     </note>
 
@@ -4743,7 +4759,7 @@ for more information.
     </note>
 
     <note id="6">
-        The failure is probably caused by the test code, harness, or configuration. Thus
+        The failure is probably caused by the test code, harness, or configuration. Thus,
         it may not affect users of the library.
     </note>
 
@@ -4825,7 +4841,7 @@ for more information.
     </note>
 
     <note id="28">
-        Unresearched failure, please contact library developers for more
+        Unresearched failure -- please contact library developers for more
         information about possible causes.
     </note>