From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.unit0.net!peer02.am4!peer.am4.highwinds-media.com!peer03.fr7!futter-mich.highwinds-media.com!news.highwinds-media.com!fx38.am4.POSTED!not-for-mail From: Felix Krause Newsgroups: comp.lang.ada Message-ID: <2018031710511851769-contact@flyx.org> References: <1b60922d-6fc1-424a-a3b2-ac667bfe71c0@googlegroups.com> <2e48bc00-5f44-499a-b56a-9bf5aad6d94f@googlegroups.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: YAML parser? User-Agent: Unison/2.2 X-Complaints-To: abuse@eweka.nl NNTP-Posting-Date: Sat, 17 Mar 2018 09:51:18 UTC Organization: Eweka Internet Services Date: Sat, 17 Mar 2018 10:51:18 +0100 X-Received-Body-CRC: 1263429432 X-Received-Bytes: 2633 Xref: reader02.eternal-september.org comp.lang.ada:51052 Date: 2018-03-17T10:51:18+01:00 List-Id: On 2018-03-17 07:17:19 +0000, mockturtle said: > Thank you, everyone. I'll try to get in touch with the mantainer of > the YAML web site to see if they can update the pate (I do not know if > there are constraints of maturity) You can ask me right here if you have concerns :). Concerning the maturity, AdaYaml is tested with the comprehensive test suite of the YAML project. The suite is still in development, but has far above 200 tests. AdaYaml passes all of the test cases relevant for a user, with failures in details where we are trying to change things for the better in upcoming YAML 1.3. The API is mostly mature, except for a possible minor change in tag handling that may happen depending on or decision process on 1.3. You can assume that AdaYaml parses all „real“ YAML 1.2 documents (i.e. not depending on a few edge cases not found anywhere in the wild) and the biggest incompatibility with 1.2 is currently that verbatim tags are not allowed: ! # fails with lexer error !!str # identical semantics, parses fine The second „incompatibility“ is that '@' is no longer reserved, but parsed as „annotation“. This will not break any existing documents as the character was previously reserved. Annotations are currently litte more than a proof-of-concept and should not concern you – if you just reject any annotation tokens, you have a normal 1.2 structure. All my experimental code is in yaml-annotation_processor.gpr so if you just import yaml.gpr, you won't import experimental code. I am always a bit lazy on crafting new releases. As I know now that there is interest in using this library again, I will wrap up the current state into a new release, as there have been some bug fixes since the last one. -- Regards, Felix Krause