On Feb 21, 2014, at 9:02 AM, Argyrios Kyrtzidis <[email protected]> wrote:
> > On Feb 21, 2014, at 3:27 AM, Dmitri Gribenko <[email protected]> wrote: > >> On Fri, Feb 21, 2014 at 12:34 AM, Ben Langmuir <[email protected]> wrote: >>> >>> On Feb 20, 2014, at 4:11 PM, Ben Langmuir <[email protected]> wrote: >>>> We could use the YAML version string >>>> %YAML 1.2 >>> >>> Actually, if we go this route we should encode our own version number in >>> the same place for compactness. In YAML, we could use a tag for this >>> >>> %TAG ! tag:vfs-yaml-file,version:1234 >>> >>> Where 1234 is a made up version number for our vfs format. >> >> Then we would need to make sure to use this tag, otherwise its >> presence or absence should not affect the semantics of the file, I >> think. Is that in the YAML spec somewhere? I don’t see it. There was something about not relying on the name of a tag handle, but I’m willing to be non-conformant in that respect. Obviously this is not what YAML tags were designed for… I’m not super happy with using a tag either, since it actually requires two lines at the top, since you apparently need a document marker (---) after your directives... %TAG ! vfs-yaml-file... --- <document> Ben _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
