[
https://issues.apache.org/jira/browse/HDFS-8766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14905513#comment-14905513
]
Haohui Mai commented on HDFS-8766:
----------------------------------
bq. Agreed. I didn't know we were using automated tools to check the code
style, I'll look into that. What's the biggest motivation for choosing Google's
C++ standards on a new project like this? The main thing that bothers me is
never using exceptions particularly in the context of constructors, I'd rather
let RAII handle cleanup and avoid lots of checks at the call site. I'm not
using much RAII at the moment because I'd like to wait until we settle on an
object ownership convention and keep it consistent throughout the library.
libhdfs++ is designed to not use C++ exceptions at all. Please do not pull in
any existing code form the legacy libhdfs3 codebase which heavily use c++
exceptions. For resource clean ups, please refer to how the {{FileSystem}}
object is implemented.
> Implement a libhdfs(3) compatible API
> -------------------------------------
>
> Key: HDFS-8766
> URL: https://issues.apache.org/jira/browse/HDFS-8766
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: hdfs-client
> Reporter: James Clampffer
> Assignee: James Clampffer
> Attachments: HDFS-8766.HDFS-8707.000.patch
>
>
> Add a synchronous API that is compatible with the hdfs.h header used in
> libhdfs and libhdfs3. This will make it possible for projects using
> libhdfs/libhdfs3 to relink against libhdfspp with minimal changes.
> This also provides a pure C interface that can be linked against projects
> that aren't built in C++11 mode for various reasons but use the same
> compiler. It also allows many other programming languages to access
> libhdfspp through builtin FFI interfaces.
> The libhdfs API is very similar to the posix file API which makes it easier
> for programs built using posix filesystem calls to be modified to access HDFS.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
