mirror of
https://github.com/google/flatbuffers.git
synced 2026-06-20 15:55:07 +00:00
Add C support in README, minor updates in other C doc
This commit is contained in:
@@ -15,8 +15,8 @@ project.
|
|||||||
|
|
||||||
- [Tutorial](@ref flatbuffers_guide_tutorial) - select C as language
|
- [Tutorial](@ref flatbuffers_guide_tutorial) - select C as language
|
||||||
when scrolling down
|
when scrolling down
|
||||||
- General Use in C (the README) <https://github.com/dvidelabs/flatcc/blob/master/README.md>
|
- General Use in C (README) <https://github.com/dvidelabs/flatcc/blob/master/README.md>
|
||||||
- The C Builder Interface, advanced <https://github.com/dvidelabs/flatcc/blob/master/doc/builder.md>
|
- The C Builder Interface (advanced) <https://github.com/dvidelabs/flatcc/blob/master/doc/builder.md>
|
||||||
|
|
||||||
|
|
||||||
## Basic Reflection
|
## Basic Reflection
|
||||||
@@ -25,7 +25,7 @@ The C-API does support reading binary schema (.bfbs)
|
|||||||
files via code generated from the `reflection.fbs` schema, and an
|
files via code generated from the `reflection.fbs` schema, and an
|
||||||
[example usage](https://github.com/dvidelabs/flatcc/tree/master/samples/reflection)
|
[example usage](https://github.com/dvidelabs/flatcc/tree/master/samples/reflection)
|
||||||
shows how to use this. The schema files are pre-generated
|
shows how to use this. The schema files are pre-generated
|
||||||
in the [runtime distribution](https://github.com/dvidelabs/flatcc/tree/master/include/flatcc/reflection). Extended reflection
|
in the [runtime distribution](https://github.com/dvidelabs/flatcc/tree/master/include/flatcc/reflection).
|
||||||
|
|
||||||
|
|
||||||
## Mutating Reflection
|
## Mutating Reflection
|
||||||
@@ -37,9 +37,12 @@ buffers using complex objects from existing buffers as source. This can
|
|||||||
be very efficient due to direct copy semantics without endian conversion or
|
be very efficient due to direct copy semantics without endian conversion or
|
||||||
temporary stack allocation.
|
temporary stack allocation.
|
||||||
|
|
||||||
|
Scalars, structs and strings can be used as source, as well vectors of
|
||||||
|
these.
|
||||||
|
|
||||||
It is currently not possible to use an existing table or vector of table
|
It is currently not possible to use an existing table or vector of table
|
||||||
as source, but it would be possible to add support for this at some
|
as source, but it would be possible to add support for this at some
|
||||||
point.
|
point. Vectors of strings
|
||||||
|
|
||||||
|
|
||||||
## Why not integrate with the `flatc` tool?
|
## Why not integrate with the `flatc` tool?
|
||||||
|
|||||||
@@ -1293,7 +1293,7 @@ like so:
|
|||||||
// The returned buffer must be deallocated using `free`.
|
// The returned buffer must be deallocated using `free`.
|
||||||
// NOTE: Finalizing the buffer does NOT change the builder, it
|
// NOTE: Finalizing the buffer does NOT change the builder, it
|
||||||
// just creates a snapshot of the builder content.
|
// just creates a snapshot of the builder content.
|
||||||
buf = flatcc_builder_finalize_buffer(&builder, &size);
|
buf = flatcc_builder_finalize_buffer(B, &size);
|
||||||
// use buf
|
// use buf
|
||||||
free(buf);
|
free(buf);
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user