From: bdawes_at_[hidden]
Date: 2008-03-26 13:07:05
Author: bemandawes
Date: 2008-03-26 13:07:04 EDT (Wed, 26 Mar 2008)
New Revision: 43871
URL: http://svn.boost.org/trac/boost/changeset/43871
Log:
Apply changeset 43864, fixing #1717
Text files modified:
branches/release/status/explicit-failures-markup.xml | 15 +++++++++++++++
1 files changed, 15 insertions(+), 0 deletions(-)
Modified: branches/release/status/explicit-failures-markup.xml
==============================================================================
--- branches/release/status/explicit-failures-markup.xml (original)
+++ branches/release/status/explicit-failures-markup.xml 2008-03-26 13:07:04 EDT (Wed, 26 Mar 2008)
@@ -3988,6 +3988,21 @@
</note>
</mark-unusable>
<mark-expected-failures>
+ <test name="object"/>
+ <toolset name="intel-10.*"/>
+ <note author="David Abrahams">
+
+ This compiler has a bug that causes silent misbehavior at runtime
+ when each of an assignment expression follows one of the following patterns:
+ <em>expr</em><code>.attr(</code><em>name</em><code>)</code>
+ or <em>expr</em><code>[</code><em>item</em><code>]</code>,
+ where <em>expr</em>
+ is-a <code>boost::python::object</code>. We've been
+ unable to find a workaround.
+
+ </note>
+ </mark-expected-failures>
+ <mark-expected-failures>
<test name="args"/>
<test name="auto_ptr"/>
<test name="builtin_convertors"/>