[
https://issues.apache.org/jira/browse/HDFS-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14252646#comment-14252646
]
Colin Patrick McCabe commented on HDFS-7018:
--------------------------------------------
bq. This brings up a good point. Should we ensure that the C++ API is
exception-free first and revisit this jira? Otherwise the binding has to wrap
every single function with catch(...).
+1 for making the C++ API exception-free.
However, I don't think we should wait for that to happen before doing this
JIRA. Another thing to consider is that even if the API never throws an
exception, standard C++ libraries can throw exceptions. The C++ runtime itself
can throw exceptions like the out-of-memory exceptions. So we would still need
the {{catch (...)}} in all the C functions in any case.
> Implement C interface for libhdfs3
> ----------------------------------
>
> Key: HDFS-7018
> URL: https://issues.apache.org/jira/browse/HDFS-7018
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: Zhanwei Wang
> Assignee: Zhanwei Wang
> Attachments: HDFS-7018-pnative.002.patch, HDFS-7018.patch
>
>
> Implement C interface for libhdfs3
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
