[
https://issues.apache.org/jira/browse/AVRO-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12715729#action_12715729
]
Doug Cutting commented on AVRO-42:
----------------------------------
Now I get:
g++ -Wall -g -I./api -I./parser -I. -isystem/usr/include/boost -c -o
obj/Compiler.o impl/Compiler.cc
In file included from ./api/Schema.hh:4,
from ./api/SymbolMap.hh:7,
from ./api/Compiler.hh:9,
from impl/Compiler.cc:1:
./api/NodeImpl.hh: In constructor 'avro::NodeRecord::NodeRecord()':
./api/NodeImpl.hh:136: error: 'numeric_limits' is not a member of 'std'
./api/NodeImpl.hh:136: error: expected primary-expression before '>' token
./api/NodeImpl.hh:136: error: '::max' has not been declared
./api/NodeImpl.hh: In constructor 'avro::NodeEnum::NodeEnum()':
./api/NodeImpl.hh:146: error: 'numeric_limits' is not a member of 'std'
./api/NodeImpl.hh:146: error: expected primary-expression before '>' token
./api/NodeImpl.hh:146: error: '::max' has not been declared
./api/NodeImpl.hh: In constructor 'avro::NodeUnion::NodeUnion()':
./api/NodeImpl.hh:179: error: 'numeric_limits' is not a member of 'std'
./api/NodeImpl.hh:179: error: expected primary-expression before '>' token
./api/NodeImpl.hh:179: error: '::max' has not been declared
make: *** [obj/Compiler.o] Error 1
> 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.