aboutsummaryrefslogtreecommitdiff
path: root/docs/source
diff options
context:
space:
mode:
authornilsocket <nilsocket@gmail.com>2019-12-02 22:01:25 +0000
committerWouter van Oortmerssen <aardappel@gmail.com>2019-12-02 14:01:25 -0800
commit58e279244c800041d0934a01ed80d9a0502170df (patch)
tree55d8faf4df834094ea188595573bef3e624e6966 /docs/source
parent3c964e10ab4f97e2a3602a8d0a8f4c402806ef89 (diff)
downloadflatbuffers-58e279244c800041d0934a01ed80d9a0502170df.tar.gz
[docs]: add missing semicolon (#5648)
Add missing semicolon for table field.
Diffstat (limited to 'docs/source')
-rw-r--r--docs/source/Schemas.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/source/Schemas.md b/docs/source/Schemas.md
index 403aebbe..bd37f418 100644
--- a/docs/source/Schemas.md
+++ b/docs/source/Schemas.md
@@ -563,7 +563,7 @@ with the new schema now cannot read nor write `a` anymore (any existing code
that tries to do so will result in compile errors), but can still read
old data (they will ignore the field).
- table { c:int a:int; b:int; }
+ table { c:int; a:int; b:int; }
This is NOT ok, as this makes the schemas incompatible. Old code reading newer
data will interpret `c` as if it was `a`, and new code reading old data