Mailing-List: contact hdfs-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-dev@hadoop.apache.org
Date: Wed, 8 Oct 2014 05:54:33 +0000 (UTC)
From: "Haohui Mai (JIRA)" <jira@apache.org>
To: hdfs-dev@hadoop.apache.org
Message-ID: <JIRA.12746622.1412747625000.215510.1412747673627@Atlassian.JIRA>
In-Reply-To: <JIRA.12746622.1412747625000@Atlassian.JIRA>
References: <JIRA.12746622.1412747625000@Atlassian.JIRA>
 <JIRA.12746622.1412747625168@arcas>
Subject: [jira] [Created] (HDFS-7207) libhdfs3 should not expose exceptions
 in public API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Haohui Mai created HDFS-7207:
--------------------------------

             Summary: libhdfs3 should not expose exceptions in public API
                 Key: HDFS-7207
                 URL: https://issues.apache.org/jira/browse/HDFS-7207
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Haohui Mai
            Priority: Blocker


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)