Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 385C117462 for ; Mon, 20 Oct 2014 20:31:37 +0000 (UTC) Received: (qmail 69716 invoked by uid 500); 20 Oct 2014 20:31:36 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 69672 invoked by uid 500); 20 Oct 2014 20:31:36 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 69653 invoked by uid 99); 20 Oct 2014 20:31:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2014 20:31:36 +0000 Date: Mon, 20 Oct 2014 20:31:36 +0000 (UTC) From: "Colin Patrick McCabe (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-7207) Consider adding a C++ API for libhdfs, libhdfs3, and libwebhdfs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-7207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-7207: --------------------------------------- Summary: Consider adding a C++ API for libhdfs, libhdfs3, and libwebhdfs (was: libhdfs3 should not expose exceptions in public C++ API) > Consider adding a C++ API for libhdfs, libhdfs3, and libwebhdfs > --------------------------------------------------------------- > > Key: HDFS-7207 > URL: https://issues.apache.org/jira/browse/HDFS-7207 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Haohui Mai > Assignee: Colin Patrick McCabe > Priority: Blocker > Attachments: HDFS-7207.001.patch > > > There are three major disadvantages of exposing exceptions in the public API: > * Exposing exceptions in public APIs forces the downstream users to be compiled with {{-fexceptions}}, which might be infeasible in many use cases. > * It forces other bindings to properly handle all C++ exceptions, which might be infeasible especially when the binding is generated by tools like SWIG. > * It forces the downstream users to properly handle all C++ exceptions, which can be cumbersome as in certain cases it will lead to undefined behavior (e.g., throwing an exception in a destructor is undefined.) -- This message was sent by Atlassian JIRA (v6.3.4#6332)