[ http://issues.apache.org/jira/browse/STDCXX-123?page=all ]
Martin Sebor reassigned STDCXX-123:
---
Assign To: Martin Sebor
EDG eccp 3.7] misconfiguration due to ill-formed C++ code in libc_decl.sh
[ http://issues.apache.org/jira/browse/STDCXX-123?page=all ]
Martin Sebor closed STDCXX-123:
---
Resolution: Fixed
Fixed by the referenced change.
EDG eccp 3.7] misconfiguration due to ill-formed C++ code in libc_decl.sh
William A. Rowe, Jr. wrote:
Martin Sebor wrote:
[...]
However, I believe that the issue can be just as effectively
dealt with by implementing the -rcN (or similar) suffix policy
that Bill mentioned in his first post, with the additional
(and IMO essential) advantage of preserving the
Liviu Nicoara wrote:
Attached is my attempt at converting the lib.string.cons test. It
contains the additional new_test.h/new.cpp and
string_test.h/string_test.cpp for support.
Do you happen to also have the test for the replacement operator new?
The current one fails with the changes to
Martin Sebor wrote:
I have no objection to tagging the 1.2.3 branch 1.2.3-rcN for each
tarball that's about to be voted on but I suspect that may not fully
address your concerns (i.e., the fact that there is a 1.2.3 branch
before an official release has taken place).
I do believe it does,
On Fri, Jan 20, 2006 at 01:39:36AM -0600, William A. Rowe, Jr. wrote:
William A. Rowe, Jr. wrote:
I do believe it does, granted the 1.2.3-rc3 branch would be internally
labeled (version id) 1.2.3, but the branch it sits on and the tarballs
it's packaged in both clearly designate 1.2.3.
