From notifications-return-52774-archive-asf-public=cust-asf.ponee.io@accumulo.apache.org Fri Nov 1 00:09:07 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id EAAEE180629 for ; Fri, 1 Nov 2019 01:09:06 +0100 (CET) Received: (qmail 82424 invoked by uid 500); 1 Nov 2019 00:09:06 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 82413 invoked by uid 99); 1 Nov 2019 00:09:06 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 01 Nov 2019 00:09:06 +0000 From: GitBox To: notifications@accumulo.apache.org Subject: [GitHub] [accumulo] ctubbsii commented on issue #1386: Update Native Maps to use more recent C++ standards Message-ID: <157256694610.12151.3402460539713632717.gitbox@gitbox.apache.org> Date: Fri, 01 Nov 2019 00:09:06 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit ctubbsii commented on issue #1386: Update Native Maps to use more recent C++ standards URL: https://github.com/apache/accumulo/issues/1386#issuecomment-548617075 Those are all very good reasons to use cmake. I'm not opposed. I just want to understand the benefits. I do wonder if it's a good idea to add third party dependencies to code which is currently very small, and has very minimal dependencies. Even if it's a performance benefit... or a maintenance benefit (less code)... it may not be worth the trade off. It'd be nice if that could be done as an independent task. As I see it, there are 3 things being discussed (and worked on) here: 1. Change the build system for the native code (make -> cmake and/or improvements to the hard-coded flags in the Makefile) 2. Modernize the code (using more recent C++ standards) 3. Reduce some of our custom code with third party libraries that do the job better In my opinion, all three of these are possibly good improvements, but they should be decoupled from one another. We're talking about making all these changes at once, and I think they each have their own pros and cons, and they should be done completely independently. That will help facilitate code reviews, and discussions about pros/cons of specific change proposals. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services