make OpenCV YAML compitable with snakeyaml ? (Bug #3167)
| Status: | Cancelled | Start date: | 2013-07-19 |
|---|---|---|---|
| Priority: | Normal | Due date: | |
| Assignee: | James Fang |
% Done: | 0% |
| Category: | core | ||
| Target version: | - | ||
| Affected version: | 2.4.0 - 2.4.7 | Operating System: | Linux |
| Difficulty: | HW Platform: | x64 | |
| Pull request: |
Description
there are two issue:
1) YAML directives should be "%YAML 1.0\n---\n" instead of "%YAML:1.0".
changing ':' to space, and append a document boundary mark.
BTW: should we also add a "..." ending boundary mark ?
2) flow style map lacks space around the ':'.
need to change from "key:value" to "key : value"
Associated revisions
Merge pull request #3167 from akarsakov:ocl_rm_clFinish
History
Updated by James Fang over 11 years ago
i just found that YAML 1.0 is using SPACE between "%YAML" and "1.0",
so issue 1) may not be valid.
But the examples from the YAML 1.0 Spec all got a space after the colon(but not before)
for flow style map.
Updated by Leonid Beynenson over 11 years ago
Hi James,
I found that in the YAML 1.1 specification (http://yaml.org/spec/1.1/index.html) in the section "Separation spaces" (http://yaml.org/spec/1.1/index.html#id893014) there is the following sentence:
Separation spaces are a presentation detail used exclusively to delineate structure and are otherwise ignored; in particular, such characters must never be considered part of a node’s content information.
So, in the YAML format using separation spaces after the colon in the pair "key:value" is not a must.
Updated by Ivan Korolev over 11 years ago
- Assignee set to James Fang
- Category set to core
- Status changed from New to Incomplete
Updated by Daniil Osokin about 11 years ago
- Affected version changed from 2.4.6 (latest release) to 2.4.0 - 2.4.7
- Status changed from Incomplete to Cancelled