Skip to content

Commit

Permalink
Merge branch 'gh-pages' into encoding-module-examples
Browse files Browse the repository at this point in the history
  • Loading branch information
zslayton authored Dec 2, 2024
2 parents 92b829e + 6c2598b commit 476fdff
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
2 changes: 1 addition & 1 deletion _books/ion-1-1/src/modules/encoding_modules.md
Original file line number Diff line number Diff line change
Expand Up @@ -237,4 +237,4 @@ $ion::(encoding)
You can also consider writing an Ion verson marker, which is more compact.
The behavior is slightly different, however:
an IVM will also add `$ion` to the encoding module sequence.
See the [Default encoding module sequence](#default-encoding-module-sequence) section for details.
See the [Default encoding module sequence](#default-encoding-module-sequence) section for details.
1 change: 1 addition & 0 deletions _books/ion-1-1/src/whats_new.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ have been supplanted by Ion 1.1's more general [opcodes](binary/opcodes.md),
which have been organized to prioritize the most commonly used encodings and make leveraging macros as inexpensive as possible.

In both text and binary Ion 1.1, the Ion Version Marker syntax is compatible with Ion 1.0's version marker syntax.

This means that an Ion 1.0-only reader can correctly identify when a stream uses Ion 1.1 (allowing it to report an error),
and an Ion 1.1 reader can correctly "downshift" to expecting Ion 1.0 data when it encounters a stream using Ion 1.0.

Expand Down

0 comments on commit 476fdff

Please sign in to comment.