You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,18 +109,26 @@ The Example will print in console the text below
109
109
```
110
110
Fields
111
111
==================
112
+
Every field can have case insensitive name which should not contain '.' (because it is reserved for links to structure field values) and '#'(because it is also reserver for inside usage).
113
+
Field name must not be started by a number or chars '$' and '_'. *Field names are case insensitive!*
114
+
```
115
+
int someNamedField;
116
+
byte field1;
117
+
byte field2;
118
+
byte field3;
119
+
```
112
120

113
121
114
-
#Primitive types
122
+
##Primitive types
115
123
The Framework supports full set of Java numeric primitives with extra types like ubyte and bit.
116
124

117
-
#Complex types
125
+
##Complex types
118
126
The Framework provides support for arrays and structures. Just keep in mind that in expressions you can make links to field values only defined before expression.
119
127

120
-
#Special types
128
+
##Special types
121
129
Special types makes some actions to skip data in input stream
122
130

123
-
#Byte order
131
+
##Byte order
124
132
Every multi-byte type can be read with different byte order.
125
133

126
134
@@ -141,10 +149,6 @@ int field1;
141
149
byte [field1+struct1.field2] data;
142
150
```
143
151
144
-
Field names
145
-
============
146
-
You can use any chars for field names but you can't use '.' in names (because the special char is used as the separator in field paths) and a name must not be started with a number. Also you must not use the symbols '$' and '_' as the first char in the name because they are used by the parser for special purposes.
147
-
148
152
Commentaries
149
153
=============
150
154
You can use commentaries inside a parser script, the parser supports the only comment format and recognizes as commentaries all text after '//' till the end of line.
0 commit comments