[ 
https://issues.apache.org/jira/browse/AVRO-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715744#action_12715744
 ] 

Scott Banachowski commented on AVRO-42:
---------------------------------------

There must be a difference in gcc compilers.  Mine doesn't seem to care about 
"#include <limits>" and must include it implicitly.  It's possible there are 
other includes, such as string, that I know are implicit but other compilers 
may care about.  I've tested it with two versions, both of which were > 4.

You can add #include<limits> to the top of api/NodeImpl.hh... but I don't know 
if you will just encounter the next thing.  In the meantime, let me see if i 
can try some other gcc versions, and create a new patch with the fixes.

> C++ avro
> --------
>
>                 Key: AVRO-42
>                 URL: https://issues.apache.org/jira/browse/AVRO-42
>             Project: Avro
>          Issue Type: New Feature
>          Components: c++
>            Reporter: Scott Banachowski
>            Assignee: Scott Banachowski
>            Priority: Minor
>         Attachments: AVRO-42.patch
>
>
> I have a C++ implementation for Avro to contribute.  I opened this issue to 
> submit a patch.
> Overview:
> Serializer/Parser- objects for writing/reading raw binary.
> xxxSchema- objects for composing schemas.
> ValidSchema- a schema object that has been converted to a parse tree (with 
> some sanity checks).
> ValidSchema.toJson() writes the schema as a json object.
> ValidatingSerializer/ValidatingParser-  check that reads/writes match the 
> expected schema type (more expensive than the raw serializer/parser but they 
> detect errors, and allow dynamic discovery of parsed data/attributes).
> Compiler (compileJsonSchema())-  converts a Json string schema to a 
> ValidSchema.
> Code Generation (experimental) - given a schema it generates C++ objects of 
> the same data types, and the code to serialize and parse it.
> What's missing: Defaults are not yet supported.  Resolving schema conflicts 
> is not yet supported.  And the file and rpc containers are not yet 
> implemented.  Documentation, sparse.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to