On Thu, 13 Feb 2025 14:12:25 -0700, Arthur Naseef <artnas...@apache.org> wrote:
| Looking at AMQCPP-628 <https://issues.apache.org/jira/browse/AMQCPP-628>, | yeah - I get it. After offering some effort and the ticket gets closed | with "won't fix" and no comments - that's discouraging. Even a comment to the effect "activemq-cpp is now a crock. Strongly suggest looking for an alternative" could have been helpful, as it would have set expectations for all the outstanding JIRAs. As it is, the subsequent AMQCPP-718 JIRA was evidently from someone who must have applied the equivalent of AMQCPP-628 and then tried to compile under C++17, uncovering the remaining issue. Of the 197 (not 196, sorry) warnings from g++ 11.4.0, 33 of them are in 13 files under main/activemq and should probably be looked into. The remaining warnings are under main/decaf and probably not worth fixing (at least on first pass). In short, having a working version that compiles on c++17 is _not_ a big deal at all, and would address (I believe) one of the most common pain points for users. | - It's unclear to me, and I suspect most of the PMC, just how much | activemq-cpp is used across the community. I suspect that participation and feedback are rare because, not to put too fine a point on it, C++ is really not welcome in a Java-centric milieu. Once the Java folks took over the ASF (around 2005 or so), C++ people have been "chased" away, in effect. There are more users than you're likely to hear about or hear from. | - Since C++ compilers are quite varied, and at Apache, the source code | is the deliverable, this also raises the question of which target | environment(s) (O/S, compiler, ...) we use internally, and which we ensure | are able to build the project (one of many things I don't miss after moving | over to the Java world). In my experience, gcc/g++ and CLang are highly compatible, so building on Linux (or the Mac) shouldn't be problematic. The issue really is Microsoft (Visual Studio), which marches to a different drum. Among various disruptive misfeatures, MS declined to follow the C++ standard guidelines and kept 'long' as a 32-bit quantity in 64-bit builds. Yes, they had their reasons, but it's an annoying headache for cross platform developers and maintainers alike. | - It would be extremely helpful (if feasible) to hear from members of | the community on their uses of the project, and what they need and care | about. I think the outstanding AMQCPP JIRAs are a fairly comprehensive list. I guess what's needed is prioritization. Arjun --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@activemq.apache.org For additional commands, e-mail: dev-h...@activemq.apache.org For further information, visit: https://activemq.apache.org/contact
