> However, I am not happy patching test-cases rather than libraries. On
> the other hand, having diagnosed the problem with a viable workaround, I
> don't see where else to record the information. Do we have a way of
> documenting known workarounds for a library?
I don't know, it seems to be a
Picking off more borland errors, I have a couple of questions on this
test case:
1/ should char be Char in the following snippet [case-error]
[Extract of static_assert.hpp starting line 53]
template
struct Bill
{
private: // can be in private, to avoid namespace pollution
BOOST_STATIC_ASS
