Skip to content

Commit 35c5b70

Browse files
Update README.md
1 parent 454fbd1 commit 35c5b70

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ flag: true
100100
```
101101
some.package.Foo 55D 455.45 236.12F T;
102102
```
103-
<br> **After introduction od variables in 1.5.0 and cope in 1.2.0:** <br>
103+
<br> *After introduction od variables in 1.1.5 and cope in 1.2.0:* <br>
104104
Serialized via **SerialX for SerialX (protocol + scope):**
105105
```
106106
some.package.Foo {
@@ -121,8 +121,8 @@ some.package.Foo {
121121
```
122122
Maybe it is a question of formating but SerialX will be the shortest one anyway. Because instead of having some sort of key to the value you simply have its order (index)!
123123
And value's data type is specified by suffix if it is a primitive data type or simply by package name as the first argument in case of an object! Other arguments (count, order, type) are then specified by a SerializationProtocol! Generally, one line means one object, one value (separated by spaces) means one argument! <br><br>
124-
Note: Since there is variable system in 1.5.0, the order of values is now not the only option to obtain an object or value! <br>
125-
Since 1.5.0 also something like this might come to mind: <br>
124+
Note: Since there is variable system in 1.1.5, the order of values is now not the only option to obtain an object or value! <br>
125+
Since 1.1.5 also something like this might come to mind: <br>
126126
```
127127
val1 = 55D;
128128
val2 = 455.45;

0 commit comments

Comments
 (0)