[
https://issues.apache.org/jira/browse/STDCXX-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483014
]
Mark Brown commented on STDCXX-364:
---
I get the same error with gcc 3.4.4 on Cygwin.
> [gcc/Linux] std::tm not decl
[
https://issues.apache.org/jira/browse/STDCXX-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483012
]
Mark Brown commented on STDCXX-351:
---
The test compiles now so your change must have fixed it.
> [gcc 3.4.6] error
> -Original Message-
> From: [EMAIL PROTECTED]
> Sent: Wed, 21 Mar 2007 16:12:57 -0600
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: [PATCH] Re: new container member functions cbegin() and
> cend()
>
> Sorry for dropping the ball on reviewing this patch.
>
> The changes look good t
> -Original Message-
> From: [EMAIL PROTECTED]
> Sent: Wed, 21 Mar 2007 09:56:30 -0600
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: [VOTE] Re: regression test suite naming convention
>
> If we constrain ourselves to the proposed options, my vote is for Option
> 2. The reason for t
[
https://issues.apache.org/jira/browse/STDCXX-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor closed STDCXX-351.
---
Rats, this is a compiler bug, not a bug in the test as I thought. Oh well, it's
also fixed in later vers
[
https://issues.apache.org/jira/browse/STDCXX-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor resolved STDCXX-351.
-
Resolution: Fixed
Fix Version/s: 4.2
I'll set the status of this to Resolved/Fixed. If I d
[
https://issues.apache.org/jira/browse/STDCXX-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Sebor reassigned STDCXX-351:
---
Assignee: Martin Sebor
> [gcc 3.4.6] error on static const int expression as an array dimensi
Sorry for dropping the ball on reviewing this patch.
The changes look good to me. The two things that are missing
and that we can't commit the patch without are: 1) tests and
2) a ChangeLog entry.
We haven't ported all the container tests to the new driver
so you won't be able to simply enhance
[EMAIL PROTECTED] wrote:
Author: ablack
Date: Tue Mar 6 14:38:21 2007
New Revision: 515332
URL: http://svn.apache.org/viewvc?view=rev&rev=515332
Log:
2007-03-05 Andrew Black <[EMAIL PROTECTED]>
* tests/src/driver.cpp (_rw_setopt_output_file): Add logic to treat
the magic file name of '-'
[
https://issues.apache.org/jira/browse/STDCXX-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482906
]
Martin Sebor commented on STDCXX-361:
-
We should still work around the bug in the test. We can't assume that ever
Farid Zaripov wrote:
-Original Message-
From: Andrew Black [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 5:57 PM
To: stdcxx-dev@incubator.apache.org
Subject: Re: [VOTE] Re: regression test suite naming convention
If we constrain ourselves to the proposed options, my vote is
> -Original Message-
> From: Andrew Black [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, March 21, 2007 5:57 PM
> To: stdcxx-dev@incubator.apache.org
> Subject: Re: [VOTE] Re: regression test suite naming convention
>
> If we constrain ourselves to the proposed options, my vote is
> for Op
Liviu Nicoara wrote:
FWIW, option 3 makes more sense to me.
It could be enhanced though in the light of Martin's reply to Mark: some
tests do not cleanly apply to a section. In which case option 3 can be
enhanced to place such tests in the regress dir w/o a section number.
I would agree with
FWIW, option 3 makes more sense to me.
It could be enhanced though in the light of Martin's reply to Mark: some
tests do not cleanly apply to a section. In which case option 3 can be
enhanced to place such tests in the regress dir w/o a section number.
Liviu
Andrew Black wrote:
If we constra
Option 3 sounds better, if option 3 is allowed. Otherwise option 2.
Yu (Scott) Zhong
-Original Message-
From: Andrew Black [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 21, 2007 9:57 AM
To: stdcxx-dev@incubator.apache.org
Subject: Re: [VOTE] Re: regression test suite naming conventi
If we constrain ourselves to the proposed options, my vote is for Option
2. The reason for this vote is because it allows us to more easily
determine what regression tests need to be run for a particular change.
If we don't constrain ourselves to the proposed options, I wish to put
forward an
I'm not hearing any yay's or nay's on the proposed convention
so how about a vote to practice our consensus building skills?
Everyone is encouraged to vote, including non-committers.
Option 1:
Put all regression tests in tests/regress/, naming each as
follows:
tests/regress/stdcxx-.cpp
Opt
17 matches
Mail list logo