[
https://issues.apache.org/jira/browse/PARQUET-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15108874#comment-15108874
]
Kalon Mills commented on PARQUET-440:
-------------------------------------
Personally, I think that exceptions are an amazing benefit of a modern
language. There are a
[lot|https://www.linkedin.com/pulse/20140503193653-3046051-why-google-style-guide-for-c-is-a-deal-breaker]
of things I don't like about the google style guide, but this is a primary
one. Googles own style guide
[states|https://google.github.io/styleguide/cppguide.html#Exceptions], "Our
advice against using exceptions is not predicated on philosophical or moral
grounds, but practical ones. ... Things would probably be different if we had
to do it all over again from scratch." While you do state some practical
reasons for not using them, to me the benefits outweigh the cons.
> Error handling: C++ exceptions or Status
> ----------------------------------------
>
> Key: PARQUET-440
> URL: https://issues.apache.org/jira/browse/PARQUET-440
> Project: Parquet
> Issue Type: New Feature
> Components: parquet-cpp
> Reporter: Wes McKinney
>
> This library currently throws C++ exceptions. I would very much prefer to use
> Google's convention of using Status objects to communicate errors and force
> explicit action to be taken on the part of the developer if an error occurs
> in a particular function call. It will also make it much easier to
> incorporate libparquet into other libraries that do not use C++ exceptions,
> and also to provide an ANSI C API wrapper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
