On Thu, 27 Feb 2025 08:29:54 -0500, Christopher Shannon
wrote:
| It's been a long time since the last release, so taking a little
| extra time and just building a 3.10.0 with more fixes seems fine
| to me, vs having to do a second release.
I agree. I've looked at the list, and am in the proce
HI Arjun,
I think it is probably worthwhile to just go ahead and include some of the
extra stuff if they are important or useful.
It's been a long time since the last release, so taking a little extra
time and just building a 3.10.0 with more fixes seems fine to me, vs having
to do a second rele
On Wed, 19 Feb 2025 11:00:20 -0500, Christopher Shannon
wrote:
| If doing that much work and bumping to upgrade for C++17 compliance
| I would at least bump the version to 3.10.0
The bump to (only) 3.9.6 was because of changes strictly needed for
compliance, and nothing else.
A bump to 3.10.0
If doing that much work and bumping to upgrade for C++17 compliance I would
at least bump the version to 3.10.0
On Tue, Feb 18, 2025 at 8:12 PM Arjun Ray wrote:
> On Sun, 16 Feb 2025 23:05:09 -0500, Arjun Ray
> wrote:
>
> | To fix this, either the file m4/find_cppunit.m4 will have to be
> | mod
On Sun, 16 Feb 2025 23:05:09 -0500, Arjun Ray
wrote:
| To fix this, either the file m4/find_cppunit.m4 will have to be
| modified - which could be non-trivial as pkg-config is not a drop-in
| replacement for cppunit-config - or we can deploy a custom version of
| cppunit-config (that basically wr
On Sun, 16 Feb 2025 20:16:56 -0700, Arthur Naseef
wrote:
| For the Strict Aliasing Rule, IIUC, the compiler is complaining about the
| (void*) cast from (Node *), right?
It's complaining about (volatile void**)(&node->next). The more I
look at this, the more mystified I get. The volatile keywo
On Sat, 15 Feb 2025 16:27:54 -0500, Arjun Ray
wrote:
| Testing has turned out to be a problem apparently with the toolset.
| For some reason the integration tests are not building at all. I'm
| not enough of an Aututools maven to see the problem right away, but I
| suspect it has to do with havi
For the Strict Aliasing Rule, IIUC, the compiler is complaining about the
(void*) cast from (Node *), right?
Is there any way two different pointer types have different sizes? If not,
I agree with the assessment that this is not harmful. The only way I can
see to fix it would be to simply inline
On Fri, 14 Feb 2025 13:29:26 -0500, Arjun Ray
wrote:
| For example, I think I'm in a position to offer a set of diffs in
| a JIRA to make the code base C++17 ready. All that would need is
| someone with privileges to commit the implied pull requests and
| test them.
Nearly there! :-)
I've
> ASF rightly does not make it easy to join projects as well.
So being a contributor is actually really easy, and you have already done a
good amount of that - both with the code contribution and this discussion
here. However, becoming a committer is a higher bar.
I was invited to become a commi
On Thu, 13 Feb 2025 16:31:26 -0600, Justin Bertram
wrote:
| I would be happy to see folks step forward and embrace responsibility
| for this code-base. If not, I'm also happy to declare this code-base
| EOL. What I'm not happy to accept is this continued limbo where valid
| problems never get
11 matches
Mail list logo
