The yaml.org site is nice because it links to the specs. (It's also
entertaining because the site itself presents as a YAML document.)
Whatever library is being used to handle YAML parsing should declare the
spec version(s) that are supported, and those spec documents helped me when
learning to us
I think I'd rather go back to the punch card approach where you put a C in
column 6 for line continuation.
On Fri, Apr 26, 2019 at 2:49 PM Walt Karas wrote:
> TL;DR love of Satan
>
> On Fri, Apr 26, 2019 at 2:48 PM Derek Dagit wrote:
>
>> I think it should be consistent.
>>
>> The first line e
TL;DR love of Satan
On Fri, Apr 26, 2019 at 2:48 PM Derek Dagit wrote:
> I think it should be consistent.
>
> The first line establishes an indentation width of 2 spaces.
>
> The second line is a list element that itself is a map of one entry, and
> your multi-line text is the value for this ent
I think it should be consistent.
The first line establishes an indentation width of 2 spaces.
The second line is a list element that itself is a map of one entry, and
your multi-line text is the value for this entry.
Since it is nested, in effect we need to indent twice, and so I think that
is w
I think a problem here is Canned YAML isn't a library, it's an application.
It reads schemas and generates C++ code. It is not itself linked in to
anything. We could actually use it completely outside of ATS and only check
in the generated code. However, the generated code depends on what is
effect
My suggestion was to add the utilities as part of Canned YAML code base and
bring in Canned YAML as a single library. I don’t think it makes sense to have
two separate libraries (libswoc and canned YAML). This way anyone who would
want to use a C++ schema validation library for YAML can easily
