Ok, thanks for the clarification.

On 22 July 2014 23:33, Oren Ben-Kiki <oren@ben-kiki.org> wrote:
Well... that's why it says "YAML 1.2 is compatible with 1.1 for most practical applications - this is a minor revision.". Directives were/are pretty rarely used in practice. There are other subtle incompatibility issues, due to the requirement of being 100% compatible with JSON.

On Wed, Jul 23, 2014 at 1:05 AM, Antoine Aubry <aaubry@gmail.com> wrote:
According to the YAML 1.1 spec,

If the document specifies no directives, it is parsed using the same settings as the previous document.

However, the YAML 1.2 spec states that

9.1. Documents
A YAML character stream may contain several documents. Each document is completely independent from the rest.

and makes no mention of inheriting directives from the previous document. This change might cause subtle bugs when using a 1.2 processor on a stream that was designed assuming version 1.1. Am I correctly interpreting the specs?

In the initial paragraphs of version 1.2, it is said that

The primary objective of this revision is to bring YAML into compliance with JSON as an official subset. YAML 1.2 is compatible with 1.1 for most practical applications - this is a minor revision.

This makes me wonder if this change was intentional, or if was an overlook. Can someone clarify?


      Antoine Aubry

Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
Yaml-core mailing list