Clarify conflicts with 'identifier'
@@ -1130,6 +1130,12 @@ If unfortunate, it is possible to have a read accessor method conflict
with other generated methods and typenames. Usually a small change in
the schema will resolve this issue.
+Especially fields named "identifier" have caused problems because the
+field read accessor function coincideds with the autogenerated
+`<table-name>_identifer` used as file identifier for buffers with the
+given table as root. This can be solved by either renaming the
+conflicting field name or by using the `-g` option:
+
As of flatcc 0.5.2 read accors are generated with and without a `_get`
suffix so it is also possible to use `Monster_pos_get(monster)` instead
of `Monster_pos(monster)`. When calling flatcc with option `-g` the
