[
https://issues.apache.org/jira/browse/HADOOP-10388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925010#comment-13925010
]
Colin Patrick McCabe commented on HADOOP-10388:
-----------------------------------------------
bq.I believe there are still no plans for the Microsoft compiler to provide
full support for the most recent C standards. If we choose C, then we might
have to stick to an old dialect, like we currently do in
libhadoop.so/hadoop.dll.
I agree. The kernel coding standard is designed around C89, which makes it
good for this use-case.
bq. VS 2013 claims C99 support. No idea whether this applies to the free
compiler included with the Windows SDK.
That link says they are going to support a few specific features. I'm not
aware of any claims that they will have full C99 support; did I miss something?
We might consider allowing designated initializers (I think the kernel coding
style makes use of them). C99 Variable-sized arrays on the stack are actually
something to avoid because you don't want stack overflows (the Google coding
standard bans them for this reason).
> Pure native hadoop client
> -------------------------
>
> Key: HADOOP-10388
> URL: https://issues.apache.org/jira/browse/HADOOP-10388
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Binglin Chang
>
> A pure native hadoop client has following use case/advantages:
> 1. writing Yarn applications using c++
> 2. direct access to HDFS, without extra proxy overhead, comparing to web/nfs
> interface.
> 3. wrap native library to support more languages, e.g. python
> 4. lightweight, small footprint compare to several hundred MB of JDK and
> hadoop library with various dependencies.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
