[EMAIL PROTECTED] wrote:
Author: faridz
Date: Wed Oct 24 05:22:17 2007
New Revision: 587873

URL: http://svn.apache.org/viewvc?rev=587873&view=rev
[...]
@@ -137,10 +138,10 @@
#endif // _RWSTD_INT64_T - std::pair<_RWSTD_INT8_T*, std::ptrdiff_t> buf0;
-    std::pair<_RWSTD_INT16_T*, std::ptrdiff_t> buf1;
-    std::pair<_RWSTD_INT32_T*, std::ptrdiff_t> buf2;
-    std::pair<Type64*,         std::ptrdiff_t> buf3;
+    std::pair<_RWSTD_INT8_T*,  std::ptrdiff_t> buf0 (0, 0);
+    std::pair<_RWSTD_INT16_T*, std::ptrdiff_t> buf1 (0, 0);
+    std::pair<_RWSTD_INT32_T*, std::ptrdiff_t> buf2 (0, 0);
+    std::pair<Type64*,         std::ptrdiff_t> buf3 (0, 0);

Why is this necessary? Shouldn't the default ctor zero out
(i.e., default-initialize) its members?

Is this is a workaround for a compiler bug? (If so, which one?)

Martin

Reply via email to