You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(101) |
Jun
(157) |
Jul
(89) |
Aug
(135) |
Sep
(17) |
Oct
(86) |
Nov
(410) |
Dec
(311) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(76) |
Feb
(100) |
Mar
(139) |
Apr
(138) |
May
(234) |
Jun
(178) |
Jul
(271) |
Aug
(286) |
Sep
(816) |
Oct
(50) |
Nov
(28) |
Dec
(137) |
2003 |
Jan
(62) |
Feb
(25) |
Mar
(97) |
Apr
(34) |
May
(35) |
Jun
(32) |
Jul
(32) |
Aug
(57) |
Sep
(67) |
Oct
(176) |
Nov
(36) |
Dec
(37) |
2004 |
Jan
(20) |
Feb
(93) |
Mar
(16) |
Apr
(36) |
May
(59) |
Jun
(48) |
Jul
(20) |
Aug
(154) |
Sep
(868) |
Oct
(41) |
Nov
(63) |
Dec
(60) |
2005 |
Jan
(59) |
Feb
(15) |
Mar
(16) |
Apr
(14) |
May
(19) |
Jun
(16) |
Jul
(25) |
Aug
(19) |
Sep
(7) |
Oct
(12) |
Nov
(18) |
Dec
(41) |
2006 |
Jan
(16) |
Feb
(65) |
Mar
(51) |
Apr
(75) |
May
(38) |
Jun
(25) |
Jul
(23) |
Aug
(16) |
Sep
(24) |
Oct
(3) |
Nov
(1) |
Dec
(10) |
2007 |
Jan
(4) |
Feb
(5) |
Mar
(7) |
Apr
(29) |
May
(38) |
Jun
(3) |
Jul
(1) |
Aug
(17) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(16) |
2008 |
Jan
(11) |
Feb
(4) |
Mar
(7) |
Apr
(48) |
May
(17) |
Jun
(9) |
Jul
(6) |
Aug
(12) |
Sep
(5) |
Oct
(7) |
Nov
(4) |
Dec
(11) |
2009 |
Jan
(15) |
Feb
(28) |
Mar
(12) |
Apr
(44) |
May
(6) |
Jun
(16) |
Jul
(6) |
Aug
(37) |
Sep
(107) |
Oct
(24) |
Nov
(30) |
Dec
(22) |
2010 |
Jan
(8) |
Feb
(16) |
Mar
(11) |
Apr
(28) |
May
(9) |
Jun
(26) |
Jul
(7) |
Aug
(25) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
(5) |
Feb
(6) |
Mar
(3) |
Apr
(2) |
May
(10) |
Jun
(44) |
Jul
(11) |
Aug
(8) |
Sep
(6) |
Oct
(42) |
Nov
(19) |
Dec
(5) |
2012 |
Jan
(23) |
Feb
(8) |
Mar
(9) |
Apr
(11) |
May
(2) |
Jun
(11) |
Jul
|
Aug
(18) |
Sep
(1) |
Oct
(15) |
Nov
(14) |
Dec
(8) |
2013 |
Jan
(5) |
Feb
(13) |
Mar
(2) |
Apr
(10) |
May
|
Jun
(6) |
Jul
(17) |
Aug
(2) |
Sep
(3) |
Oct
|
Nov
(11) |
Dec
|
2014 |
Jan
|
Feb
(1) |
Mar
(10) |
Apr
(12) |
May
(1) |
Jun
(9) |
Jul
(27) |
Aug
(5) |
Sep
(13) |
Oct
(9) |
Nov
(9) |
Dec
|
2015 |
Jan
(8) |
Feb
(5) |
Mar
(1) |
Apr
(10) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(2) |
Oct
(14) |
Nov
(1) |
Dec
(6) |
2016 |
Jan
(12) |
Feb
(12) |
Mar
(133) |
Apr
(7) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(3) |
Nov
(5) |
Dec
|
2017 |
Jan
(2) |
Feb
|
Mar
(3) |
Apr
|
May
(1) |
Jun
(8) |
Jul
(2) |
Aug
(2) |
Sep
(8) |
Oct
(2) |
Nov
(8) |
Dec
(1) |
2018 |
Jan
(1) |
Feb
(2) |
Mar
(6) |
Apr
|
May
(1) |
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
(2) |
Feb
(2) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(2) |
2020 |
Jan
(5) |
Feb
|
Mar
(2) |
Apr
(6) |
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2021 |
Jan
(5) |
Feb
(2) |
Mar
(6) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
|
Aug
(5) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(4) |
2022 |
Jan
(1) |
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(3) |
Nov
(1) |
Dec
(1) |
2023 |
Jan
|
Feb
(1) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Peter M. <pet...@gm...> - 2021-10-01 21:19:45
|
Ingy, Tina and others, Congratulations and thank you. Best regards, Peter On Fri, Oct 1, 2021 at 11:06 PM Ingy dot Net <in...@in...> wrote: > Greetings, > > We are excited to announce the release of Revision 1.2.2 of the YAML 1.2 > Specification <https://yaml.org/spec/1.2.2/>. This revision comes 12 > years to the day after the previous revision > <https://yaml.org/spec/1.2.1/>. > > Highlights of this revision include: > > > - > > No normative changes from the 1.2.1 revision. YAML 1.2 has not been > changed. > - > > Hundreds of changes to improve clarity and readability and remove > ambiguity. > - > > Syntax productions are revised to simplify the trickier parts. The > parameterized BNF used by the spec is now fully documented. > - > > Spec links to a set of companion pages with useful information for > implementers and application developers. These pages will be continually > updated between spec revisions. > - > > Spec sources <https://github.com/yaml/yaml-spec/> are hosted publicly > on GitHub. > - > > Every change from the 1.2.1 spec came as a team-reviewed pull request > <https://github.com/yaml/yaml-spec/pulls>. > - > > Spec sources are in Markdown > <https://raw.githubusercontent.com/yaml/yaml-spec/main/spec/1.2.2/spec.md> > instead of DocBook > <https://github.com/yaml/yaml-spec/tree/main/spec/2009/> with hopes of > easing contribution. > - > > Diagram images are now SVG > <https://github.com/yaml/www.yaml.org/tree/gh-pages/spec/1.2.2/img> > rendered from LaTeX > <https://github.com/yaml/yaml-spec/tree/main/spec/1.2.2/src>, for > contribution without special software. > - > > Fully containerized build systems. Run `make serve` in your fork to > see local changes. > > > This revision is the result of years of work by the new YAML language > development team <https://yaml.org/spec/1.2.2/ext/team/>. Each person on > this team has a deep knowledge of the language and has written and > maintains important open source YAML frameworks and tools. Much like the original > YAML team <https://yaml.org/spec/1.2.2/ext/team/>, they bring diverse > ideas to the table and argue over every detail, but always with a respect > for the team. > > The team is excited to take YAML and its toolchains into the future. We > know that despite its large and growing popularity, the YAML ecosystem has > many problems. We see the various ways that projects are trying to extend > the language or work around its quirks. We see a future where YAML: > > > - > > Becomes richer and more expressive, while not breaking today’s YAML. > - > > Achieves lossless data transfer between frameworks in any language. > - > > Has frameworks that offer full functionality, and yet are easier to > write and maintain. > > > It’s a tall order, but we’ve been working on it for years and we see the > path forward. We’re not only working out the ways to specify the future > YAML, we are building working reference frameworks > <https://github.com/yaml/yaml-reference-parser#readme> and tools in sync. > We have interactive browser demos > <https://spec.yaml.io/main/playground/parser> for these reference > implementations so everyone can try things out and point out any problems. > > Speaking of communication, we have a few social sites to mention: > > > - > > YAML Matrix group chat <https://matrix.to/#/%23chat:yaml.io> is where > YAML users and developers now gather. Join us! > - > > Follow the latest YAML happenings on @yamlnews > <https://twitter.com/yamlnews> Twitter. > - > > Check out the YAML Blog <https://yaml.com/blog/>. > > > Excited for YAML, > > — Ingy, Tina, Panto, Eemeli and Thom > > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core > -- Email: pet...@gm... WWW: http://www.pkmurphy.com.au/ |
From: Ingy d. N. <in...@in...> - 2021-10-01 13:06:06
|
Greetings, We are excited to announce the release of Revision 1.2.2 of the YAML 1.2 Specification <https://yaml.org/spec/1.2.2/>. This revision comes 12 years to the day after the previous revision <https://yaml.org/spec/1.2.1/>. Highlights of this revision include: - No normative changes from the 1.2.1 revision. YAML 1.2 has not been changed. - Hundreds of changes to improve clarity and readability and remove ambiguity. - Syntax productions are revised to simplify the trickier parts. The parameterized BNF used by the spec is now fully documented. - Spec links to a set of companion pages with useful information for implementers and application developers. These pages will be continually updated between spec revisions. - Spec sources <https://github.com/yaml/yaml-spec/> are hosted publicly on GitHub. - Every change from the 1.2.1 spec came as a team-reviewed pull request <https://github.com/yaml/yaml-spec/pulls>. - Spec sources are in Markdown <https://raw.githubusercontent.com/yaml/yaml-spec/main/spec/1.2.2/spec.md> instead of DocBook <https://github.com/yaml/yaml-spec/tree/main/spec/2009/> with hopes of easing contribution. - Diagram images are now SVG <https://github.com/yaml/www.yaml.org/tree/gh-pages/spec/1.2.2/img> rendered from LaTeX <https://github.com/yaml/yaml-spec/tree/main/spec/1.2.2/src>, for contribution without special software. - Fully containerized build systems. Run `make serve` in your fork to see local changes. This revision is the result of years of work by the new YAML language development team <https://yaml.org/spec/1.2.2/ext/team/>. Each person on this team has a deep knowledge of the language and has written and maintains important open source YAML frameworks and tools. Much like the original YAML team <https://yaml.org/spec/1.2.2/ext/team/>, they bring diverse ideas to the table and argue over every detail, but always with a respect for the team. The team is excited to take YAML and its toolchains into the future. We know that despite its large and growing popularity, the YAML ecosystem has many problems. We see the various ways that projects are trying to extend the language or work around its quirks. We see a future where YAML: - Becomes richer and more expressive, while not breaking today’s YAML. - Achieves lossless data transfer between frameworks in any language. - Has frameworks that offer full functionality, and yet are easier to write and maintain. It’s a tall order, but we’ve been working on it for years and we see the path forward. We’re not only working out the ways to specify the future YAML, we are building working reference frameworks <https://github.com/yaml/yaml-reference-parser#readme> and tools in sync. We have interactive browser demos <https://spec.yaml.io/main/playground/parser> for these reference implementations so everyone can try things out and point out any problems. Speaking of communication, we have a few social sites to mention: - YAML Matrix group chat <https://matrix.to/#/#chat:yaml.io> is where YAML users and developers now gather. Join us! - Follow the latest YAML happenings on @yamlnews <https://twitter.com/yamlnews> Twitter. - Check out the YAML Blog <https://yaml.com/blog/>. Excited for YAML, — Ingy, Tina, Panto, Eemeli and Thom |
From: Ingy d. N. <in...@in...> - 2021-10-01 12:43:46
|
Greetings, We are excited to announce the release of Revision 1.2.2 of the YAML 1.2 Specification <https://yaml.org/spec/1.2.2/>. This revision comes 12 years to the day after the previous revision <https://yaml.org/spec/1.2.1/>. Highlights of this revision include: - No normative changes from the 1.2.1 revision. YAML 1.2 has not been changed. - Hundreds of changes to improve clarity and readability and remove ambiguity. - Syntax productions are revised to simplify the trickier parts. The parameterized BNF used by the spec is now fully documented. - Spec links to a set of companion pages with useful information for implementers and application developers. These pages will be continually updated between spec revisions. - Spec sources <https://github.com/yaml/yaml-spec/> are hosted publicly on GitHub. - Every change from the 1.2.1 spec came as a team-reviewed pull request <https://github.com/yaml/yaml-spec/pulls>. - Spec sources are in Markdown <https://raw.githubusercontent.com/yaml/yaml-spec/main/spec/1.2.2/spec.md> instead of DocBook <https://github.com/yaml/yaml-spec/tree/main/spec/2009/> with hopes of easing contribution. - Diagram images are now SVG <https://github.com/yaml/www.yaml.org/tree/gh-pages/spec/1.2.2/img> rendered from LaTeX <https://github.com/yaml/yaml-spec/tree/main/spec/1.2.2/src>, for contribution without special software. - Fully containerized build systems. Run `make serve` in your fork to see local changes. This revision is the result of years of work by the new YAML language development team <https://yaml.org/spec/1.2.2/ext/team/>. Each person on this team has a deep knowledge of the language and has written and maintains important open source YAML frameworks and tools. Much like the original YAML team <https://yaml.org/spec/1.2.2/ext/team/>, they bring diverse ideas to the table and argue over every detail, but always with a respect for the team. The team is excited to take YAML and its toolchains into the future. We know that despite its large and growing popularity, the YAML ecosystem has many problems. We see the various ways that projects are trying to extend the language or work around its quirks. We see a future where YAML: - Becomes richer and more expressive, while not breaking today’s YAML. - Achieves lossless data transfer between frameworks in any language. - Has frameworks that offer full functionality, and yet are easier to write and maintain. It’s a tall order, but we’ve been working on it for years and we see the path forward. We’re not only working out the ways to specify the future YAML, we are building working reference frameworks <https://github.com/yaml/yaml-reference-parser#readme> and tools in sync. We have interactive browser demos <https://spec.yaml.io/main/playground/parser> for these reference implementations so everyone can try things out and point out any problems. Speaking of communication, we have a few social sites to mention: - YAML Matrix group chat <https://matrix.to/#/#chat:yaml.io> is where YAML users and developers now gather. Join us! - Follow the latest YAML happenings on @yamlnews <https://twitter.com/yamlnews> Twitter. - Check out the YAML Blog <https://yaml.com/blog/>. Excited for YAML, — Ingy, Tina, Panto, Eemeli and Thom |
From: David T. <hd...@gm...> - 2021-08-21 20:39:45
|
Thanks for the information, Ingy! I should have realized that the list isn't used much just by the lack of traffic, but I didn't know where to look. And thanks to the pointer to libfyaml. I hadn't seen that package (or, at least hadn't noted it) in by browsing, but just looking at the excellent Readme.md, it looks like it's well documented and functional. I'll give it a try. David On 8/21/21 8:33 AM, Ingy dot Net wrote: > Greetings, > > This mailing list isn't used for much anymore, save high level > announcements from time to time. > > A couple things: > > * Check out https://github.com/pantoniou/libfyaml/ > <https://github.com/pantoniou/libfyaml/> which is more full > featured and under active development. > * Join https://matrix.to/#/#chat:yaml.io > <https://matrix.to/#/#chat:yaml.io> which is the new best way to > engage with the YAML community. > o #yaml IRC is still around on the libera.chat IRC network. > > Cheers, Ingy > > > On Mon, Aug 16, 2021 at 12:19 PM Felix Krause <ya...@fl... > <mailto:ya...@fl...>> wrote: > > Hi David, > > libyaml does contain such an API: > https://github.com/yaml/libyaml/blob/master/include/yaml.h#L1457 > <https://github.com/yaml/libyaml/blob/master/include/yaml.h#L1457> > > This gives you a |yaml_document_t| with a root node accessible via > |yaml_document_get_root_node|. The API is not well-documented but > basically nodes can refer to sub-nodes via an |int| index and you > use |yaml_document_get_node| to retrieve subnodes. > > mapping and sequence nodes store their children in a stack > structure – you iterate them via > > |for (yaml_node_item_t *cur = node->data.sequence.start; cur != > node->data.sequence.top; ++cur) { // ... } | > > Now if you load in a YAML that contains a mapping with scalar > key/value pairs, your root node will be a mapping and the subnodes > will be scalars. > > ------------------------------------------------------------------------ > > If you want a more convenient API, I did write this utility in the > past: https://github.com/flyx/libyaml_constructor > <https://github.com/flyx/libyaml_constructor> > > It is a code generator that reads in a C header containing type > definitions and autogenerates code that loads YAML into those > types (using libyaml). With this, you can define how your YAML > structure must look via C types and some annotations in the given > header. > > That tool was a part of a project which I abandoned, hence I never > did a proper release. However it did work quite well for all I can > remember. The compile-time dependency on libclang (to parse your C > header) may be a bit of a hurdle. > > Cheers, > Felix > > _______________________________________________ > Yaml-core mailing list > Yam...@li... > <mailto:Yam...@li...> > https://lists.sourceforge.net/lists/listinfo/yaml-core > <https://lists.sourceforge.net/lists/listinfo/yaml-core> > |
From: Ingy d. N. <in...@in...> - 2021-08-21 13:28:54
|
Greetings, This mailing list isn't used for much anymore, save high level announcements from time to time. A couple things: - Check out https://github.com/pantoniou/libfyaml/ which is more full featured and under active development. - Join https://matrix.to/#/#chat:yaml.io which is the new best way to engage with the YAML community. - #yaml IRC is still around on the libera.chat IRC network. Cheers, Ingy On Mon, Aug 16, 2021 at 12:19 PM Felix Krause <ya...@fl...> wrote: > Hi David, > > libyaml does contain such an API: > https://github.com/yaml/libyaml/blob/master/include/yaml.h#L1457 > > This gives you a yaml_document_t with a root node accessible via > yaml_document_get_root_node. The API is not well-documented but basically > nodes can refer to sub-nodes via an int index and you use > yaml_document_get_node to retrieve subnodes. > > mapping and sequence nodes store their children in a stack structure – you > iterate them via > > for (yaml_node_item_t *cur = node->data.sequence.start; cur != node->data.sequence.top; ++cur) { > // ... > } > > Now if you load in a YAML that contains a mapping with scalar key/value > pairs, your root node will be a mapping and the subnodes will be scalars. > ------------------------------ > > If you want a more convenient API, I did write this utility in the past: > https://github.com/flyx/libyaml_constructor > > It is a code generator that reads in a C header containing type > definitions and autogenerates code that loads YAML into those types (using > libyaml). With this, you can define how your YAML structure must look via C > types and some annotations in the given header. > > That tool was a part of a project which I abandoned, hence I never did a > proper release. However it did work quite well for all I can remember. The > compile-time dependency on libclang (to parse your C header) may be a bit > of a hurdle. > > Cheers, > Felix > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core > |
From: Felix K. <ya...@fl...> - 2021-08-16 19:19:36
|
Hi David, libyaml does contain such an API: https://github.com/yaml/libyaml/blob/master/include/yaml.h#L1457 This gives you a `yaml_document_t` with a root node accessible via `yaml_document_get_root_node`. The API is not well-documented but basically nodes can refer to sub-nodes via an `int` index and you use `yaml_document_get_node` to retrieve subnodes. mapping and sequence nodes store their children in a stack structure – you iterate them via ``` for (yaml_node_item_t *cur = node->data.sequence.start; cur != node->data.sequence.top; ++cur) { // ... } ``` Now if you load in a YAML that contains a mapping with scalar key/value pairs, your root node will be a mapping and the subnodes will be scalars. --- If you want a more convenient API, I did write this utility in the past: https://github.com/flyx/libyaml_constructor It is a code generator that reads in a C header containing type definitions and autogenerates code that loads YAML into those types (using libyaml). With this, you can define how your YAML structure must look via C types and some annotations in the given header. That tool was a part of a project which I abandoned, hence I never did a proper release. However it did work quite well for all I can remember. The compile-time dependency on libclang (to parse your C header) may be a bit of a hurdle. Cheers, Felix |
From: Oliver F. <o.b...@sw...> - 2021-08-15 08:53:03
|
Hi David, did you have a look at the available libraries for C and C++ listed at https://yaml.org/? Oliver Am 13.08.21 um 23:22 schrieb David Todd: > Apologies in advance: couldn't see a way to reply to prior thread on > the Sourceforge mailing list site so I'm repeating here. > > In 2011 (!), @wuttke and @simonov exchanged email about simpler ways > of loading yaml files. > > *Re: [Yaml-core] can I load entire node trees with the C library > libyaml ? <https://sourceforge.net/p/yaml/mailman/message/28445947/>* > From: Kirill Simonov <xi@re...> - 2011-11-24 15:23:20 > Hi Joachim, > > A high-level API for libyaml was planned, but never finished. I wasn't > able to design a satisfactory high-level API for C and it appeared to be > easier to expose the low-level interface and construct the document tree > in a scripting language. > > On 11/17/2011 03:37 AM, Joachim Wuttke<j.wuttke@...> wrote: > > So far, the best introduction to libyaml I found is > > the tutorial by Andrew Poelstra at > > http://wpsoftware.net/andrew/pages/libyaml.html <http://wpsoftware.net/andrew/pages/libyaml.html> > > It explains two ways of parsing a YAML file, by > > token or by event. Both are pretty low level; if > > I understand correctly, parsing by event is just > > a little less low level than parsing by token. > > > > In contrast, scripting languages offer a much > > simpler way of loading YAML files, basically: > > y = YAML.load( URL.open("http://yaml.org";) ) > > print y["Projects"]["C/C++ Libraries"][0] > > would yield "libyaml". > > > > Is it possible under C to load in a similar way > > an entire YAML file into a node tree? > > > > There is a yaml_node_type_t, is there any example > > how to use it? > > > > Thanks in advance, Joachim > > > > > I have a similar question, but in a C program context. I'm interested > in parsing YAML into a tree of key:value nodes for subsequent > retrieval and processing. > > For a prior project I used XML and libxml2 > (http://xmlsoft.org/example.html), and while XML has some advantages, > YAML is much more readable and (perhaps) easier to code. > > libxml2 has a number of tools, including an XML parser that yields a > tree and functions to retrieve values from the tree given a key and > starting node. > > Has anyone created such a package for YAML? If so, would you be > willing to share it? > > If not, would there be any value to others (apparently not, if no one > has done it). It seems that it might be relatively easy to generate > the tree from the existing run-parse-tree-suite.c code (though I'm > sufficiently new to YAML, and have a very limited use case, that > that's probably a naive statement). > > Thanks for any help you can offer. > > David > > > > > > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core -- N Oliver B. Fischer A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany P +49 30 44793251 M +49 178 7903538 E o.b...@sw... S oliver.b.fischer J oli...@ja... X http://xing.to/obf |
From: David T. <hd...@gm...> - 2021-08-13 21:22:21
|
Apologies in advance: couldn't see a way to reply to prior thread on the Sourceforge mailing list site so I'm repeating here. In 2011 (!), @wuttke and @simonov exchanged email about simpler ways of loading yaml files. *Re: [Yaml-core] can I load entire node trees with the C library libyaml ? <https://sourceforge.net/p/yaml/mailman/message/28445947/>* From: Kirill Simonov <xi@re...> - 2011-11-24 15:23:20 Hi Joachim, A high-level API for libyaml was planned, but never finished. I wasn't able to design a satisfactory high-level API for C and it appeared to be easier to expose the low-level interface and construct the document tree in a scripting language. On 11/17/2011 03:37 AM, Joachim Wuttke <j.wuttke@...> wrote: > So far, the best introduction to libyaml I found is > the tutorial by Andrew Poelstra at > http://wpsoftware.net/andrew/pages/libyaml.html <http://wpsoftware.net/andrew/pages/libyaml.html> > It explains two ways of parsing a YAML file, by > token or by event. Both are pretty low level; if > I understand correctly, parsing by event is just > a little less low level than parsing by token. > > In contrast, scripting languages offer a much > simpler way of loading YAML files, basically: > y = YAML.load( URL.open("http://yaml.org";) ) > print y["Projects"]["C/C++ Libraries"][0] > would yield "libyaml". > > Is it possible under C to load in a similar way > an entire YAML file into a node tree? > > There is a yaml_node_type_t, is there any example > how to use it? > > Thanks in advance, Joachim > I have a similar question, but in a C program context. I'm interested in parsing YAML into a tree of key:value nodes for subsequent retrieval and processing. For a prior project I used XML and libxml2 (http://xmlsoft.org/example.html), and while XML has some advantages, YAML is much more readable and (perhaps) easier to code. libxml2 has a number of tools, including an XML parser that yields a tree and functions to retrieve values from the tree given a key and starting node. Has anyone created such a package for YAML? If so, would you be willing to share it? If not, would there be any value to others (apparently not, if no one has done it). It seems that it might be relatively easy to generate the tree from the existing run-parse-tree-suite.c code (though I'm sufficiently new to YAML, and have a very limited use case, that that's probably a naive statement). Thanks for any help you can offer. David |
From: Carsten B. <ca...@tz...> - 2021-06-22 17:55:16
|
It is probably best to publish a short errata sheet for 1.2 and then a 1.2.1 with those fixed. Grüße, Carsten > On 2021-06-22, at 19:08, Tina Müller <po...@ti...> wrote: > > Hi Max, > > On Tue, 22 Jun 2021, Max-Julian Pogner wrote: > >> >> In the YAML Specification 1.2 3rd edition (patched 2009-10-01)[*] in >> "Example 6.1. Indentation Spaces" >> the right green block shows a start of document marker as "- - -". Other examples only show "---", and section 2.2. Stuctures also only mentions "---". Finally, section 9.1.2 Document Markers allows in its BNF 203 no possibility for a space or spaces between the dashes. >> >>> [203] c-directives-end ::= “-” “-” “-” >> >> >> Am i missing something, or should the example 6.1. be updated so that the document start marker is also "---" there? > > Thanks, that is a mistake. > > We are currently working on the spec, getting it into other formats for future > versions (mainly Ingy is working on this), and we're not sure if we > should touch the original spec (there are actually more mistakes), or > publish a 1.2.1 version with fixed typos. > > cheers, > tina_______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core |
From: Tina M. <po...@ti...> - 2021-06-22 17:21:24
|
Hi Max, On Tue, 22 Jun 2021, Max-Julian Pogner wrote: > > In the YAML Specification 1.2 3rd edition (patched 2009-10-01)[*] in > "Example 6.1. Indentation Spaces" > the right green block shows a start of document marker as "- - -". Other > examples only show "---", and section 2.2. Stuctures also only mentions > "---". Finally, section 9.1.2 Document Markers allows in its BNF 203 no > possibility for a space or spaces between the dashes. > >> [203] c-directives-end ::= “-” “-” “-” > > > Am i missing something, or should the example 6.1. be updated so that the > document start marker is also "---" there? Thanks, that is a mistake. We are currently working on the spec, getting it into other formats for future versions (mainly Ingy is working on this), and we're not sure if we should touch the original spec (there are actually more mistakes), or publish a 1.2.1 version with fixed typos. cheers, tina |
From: Max-Julian P. <max...@po...> - 2021-06-22 16:56:57
|
Hi there, In the YAML Specification 1.2 3rd edition (patched 2009-10-01)[*] in "Example 6.1. Indentation Spaces" the right green block shows a start of document marker as "- - -". Other examples only show "---", and section 2.2. Stuctures also only mentions "---". Finally, section 9.1.2 Document Markers allows in its BNF 203 no possibility for a space or spaces between the dashes. > [203] c-directives-end ::= “-” “-” “-” Am i missing something, or should the example 6.1. be updated so that the document start marker is also "---" there? with best regards, Max [*] https://yaml.org/spec/1.2/spec.html |
From: Earl W. <ear...@ic...> - 2021-05-09 21:55:56
|
Sent from my iPhone |
From: adamlaska <ada...@gm...> - 2021-04-08 18:26:26
|
From: Chet M. <mur...@gm...> - 2021-03-24 04:31:36
|
Is there a "most canonical YAML parser" ? I downloaded yaml2yeast, and the output ..... isn't exactly what I'm looking for, as a way of being able to enter YAML and learn if it is correct or not. Thanks, --chet-- |
From: Carsten B. <ca...@tz...> - 2021-03-23 19:36:59
|
On 23. Mar 2021, at 16:02, Tom Corcoran <bo...@gm...> wrote: > > I have since learned that YAML is a dead language, not maintained for over 10 years, which seem strange considering how much it's used these days. It would be a dead language if it weren’t spoken. But as you notice, it is spoken a lot. > On Thu, 18 Mar 2021 at 21:50, Tom Corcoran <bo...@gm... <mailto:bo...@gm...>> wrote: > I have an anchor as follows: > > helm-install > docker-flags: &my_docker_flags > - "--network host" > - "--env KUBECONFIG=/tmp/admin.conf" > - "--env HOME=${env.HOME}" > - "--volume ${env.KUBECONFIG}:/tmp/admin.conf:ro" > - "--volume ${env.PWD}:${env.PWD}" > - "--volume ${env.HOME}/.helm:${env.HOME}/.helm" > - "--volume ${var.docker_config_basepath}:${var.docker_config_basepath}" > > later I want to do: > > docker-flags: > <<: *d my_docker_flags > - "--env K8_NAMESPACE=${env.K8_NAMESPACE}" > > But, the last line is flagged as bad indentation of a mapping entry YAML What are you trying to do? I can’t parse the above. Grüße, Carsten |
From: Tom C. <bo...@gm...> - 2021-03-23 15:03:26
|
I have since learned that YAML is a dead language, not maintained for over 10 years, which seem strange considering how much it's used these days. On Thu, 18 Mar 2021 at 21:50, Tom Corcoran <bo...@gm...> wrote: > I have an anchor as follows: > > helm-install > docker-flags: &my_docker_flags > - "--network host" > - "--env KUBECONFIG=/tmp/admin.conf" > - "--env HOME=${env.HOME}" > - "--volume ${env.KUBECONFIG}:/tmp/admin.conf:ro" > - "--volume ${env.PWD}:${env.PWD}" > - "--volume ${env.HOME}/.helm:${env.HOME}/.helm" > - "--volume > ${var.docker_config_basepath}:${var.docker_config_basepath}" > > later I want to do: > > docker-flags: > <<: *d my_docker_flags > - "--env K8_NAMESPACE=${env.K8_NAMESPACE}" > > But, the last line is flagged as bad indentation of a mapping entry YAML > > Have I come across a limitation? > |
From: Ian P. <are...@gm...> - 2021-03-22 21:05:11
|
I am using LibYAML for the first time, and I can't figure out how the library reports parser errors to the application. Looking at yaml.h, I can see the "Error Handling" members of struct yaml_parser_s, but I also see: All members are internal. Manage the structure using the yaml_parser_ family of functions. But it don't see any yaml_parser_ functions that have anything to do with error handling. How then am I supposed to access these members? If (contrary to what the header says), I am supposed to access these members directly, how can I know when they contain usable information? (Links to documentation happily accepted. I haven't been able to find anything about LibYAML error handling anywhere.) -- ======================================================================== In Soviet Russia, Google searches you! ======================================================================== |
From: Tom C. <bo...@gm...> - 2021-03-18 21:51:08
|
I have an anchor as follows: helm-install docker-flags: &my_docker_flags - "--network host" - "--env KUBECONFIG=/tmp/admin.conf" - "--env HOME=${env.HOME}" - "--volume ${env.KUBECONFIG}:/tmp/admin.conf:ro" - "--volume ${env.PWD}:${env.PWD}" - "--volume ${env.HOME}/.helm:${env.HOME}/.helm" - "--volume ${var.docker_config_basepath}:${var.docker_config_basepath}" later I want to do: docker-flags: <<: *d my_docker_flags - "--env K8_NAMESPACE=${env.K8_NAMESPACE}" But, the last line is flagged as bad indentation of a mapping entry YAML Have I come across a limitation? |
From: Chet M. <mur...@gm...> - 2021-03-07 20:53:54
|
That is to say, to ask "why such-and-such was done thus in the spec ?" |
From: Đức T. P. <duc...@gm...> - 2021-02-20 11:54:11
|
From: Masoud S. <mas...@gm...> - 2021-02-15 11:34:15
|
From: Eemeli A. <ee...@gm...> - 2021-01-21 13:10:56
|
undefined On Wed, 20 Jan 2021 at 20:52, Isha Fazil 1E <ich...@gm...> wrote: > > -- > null > _______________________________________________ > Yaml-core mailing list > Yam...@li... > https://lists.sourceforge.net/lists/listinfo/yaml-core |
From: Matt D. <mr...@re...> - 2021-01-20 22:14:36
|
======================= Announcing PyYAML-5.4.1 ======================= A new release of PyYAML is now available: https://github.com/yaml/pyyaml/releases/tag/5.4.1 This release contains a fix for AttributeError during module import in some mixed version installations. PyYAML 5.4.1 will be the last release to support Python 2.7 (except for possible critical bug fix releases). Changes ======= * https://github.com/yaml/pyyaml/pull/480 -- Fix stub compat with older pyyaml versions that may unwittingly load it Resources ========= PyYAML IRC Channel: #pyyaml on irc.freenode.net PyYAML homepage: https://github.com/yaml/pyyaml PyYAML documentation: http://pyyaml.org/wiki/PyYAMLDocumentation Source and binary installers: https://pypi.org/project/PyYAML/ GitHub repository: https://github.com/yaml/pyyaml/ Bug tracking: https://github.com/yaml/pyyaml/issues YAML homepage: http://yaml.org/ YAML-core mailing list: http://lists.sourceforge.net/lists/listinfo/yaml-core About PyYAML ============ YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. PyYAML features a complete YAML 1.1 parser, Unicode support, pickle support, capable extension API, and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistence. Example ======= ``` >>> import yaml >>> yaml.full_load(""" ... name: PyYAML ... description: YAML parser and emitter for Python ... homepage: https://github.com/yaml/pyyaml ... keywords: [YAML, serialization, configuration, persistence, pickle] ... """) {'keywords': ['YAML', 'serialization', 'configuration', 'persistence', 'pickle'], 'homepage': 'https://github.com/yaml/pyyaml', 'description': 'YAML parser and emitter for Python', 'name': 'PyYAML'} >>> print(yaml.dump(_)) name: PyYAML homepage: https://github.com/yaml/pyyaml description: YAML parser and emitter for Python keywords: [YAML, serialization, configuration, persistence, pickle] ``` Maintainers =========== The following people are currently responsible for maintaining PyYAML: * Ingy döt Net * Matt Davis and many thanks to all who have contributed! See: https://github.com/yaml/pyyaml/pulls Copyright ========= Copyright (c) 2017-2021 Ingy döt Net <in...@in...> Copyright (c) 2006-2016 Kirill Simonov <xi...@re...> The PyYAML module was written by Kirill Simonov <xi...@re...>. It is currently maintained by the YAML and Python communities. PyYAML is released under the MIT license. See the file LICENSE for more details. |
From: Isha F. 1E <ich...@gm...> - 2021-01-20 18:52:27
|
-- null |
From: Matt D. <mr...@re...> - 2021-01-20 01:08:32
|
===================== Announcing PyYAML-5.4 ===================== A new release of PyYAML is now available: https://github.com/yaml/pyyaml/releases/tag/5.4 This release contains a security fix for CVE-2020-14343. It removes the python/module, python/object, and python/object/new tags from the FullLoader. YAML that uses these tags must be loaded by UnsafeLoader, or a custom loader that has explicitly enabled them. This release also adds Python wheels for manylinux1 (x86_64) and MacOS (x86_64) with the libyaml extension included (built on libyaml 0.2.5). PyYAML 5.4 will be the last release to support Python 2.7 (except for possible critical bug fix releases). Changes ======= * https://github.com/yaml/pyyaml/pull/407 -- build modernization, remove distutils, fix metadata, build wheels, CI to GHA * https://github.com/yaml/pyyaml/pull/472 -- fix for CVE-2020-14343, moves arbitrary python tags to UnsafeLoader * https://github.com/yaml/pyyaml/pull/441 -- fix memory leak in implicit resolver setup * https://github.com/yaml/pyyaml/pull/392 -- fix py2 copy support for timezone objects * https://github.com/yaml/pyyaml/pull/378 -- fix compatibility with Jython Resources ========= PyYAML IRC Channel: #pyyaml on irc.freenode.net PyYAML homepage: https://github.com/yaml/pyyaml PyYAML documentation: http://pyyaml.org/wiki/PyYAMLDocumentation Source and binary installers: https://pypi.org/project/PyYAML/ GitHub repository: https://github.com/yaml/pyyaml/ Bug tracking: https://github.com/yaml/pyyaml/issues YAML homepage: http://yaml.org/ YAML-core mailing list: http://lists.sourceforge.net/lists/listinfo/yaml-core About PyYAML ============ YAML is a data serialization format designed for human readability and interaction with scripting languages. PyYAML is a YAML parser and emitter for Python. PyYAML features a complete YAML 1.1 parser, Unicode support, pickle support, capable extension API, and sensible error messages. PyYAML supports standard YAML tags and provides Python-specific tags that allow to represent an arbitrary Python object. PyYAML is applicable for a broad range of tasks from complex configuration files to object serialization and persistence. Example ======= ``` >>> import yaml >>> yaml.full_load(""" ... name: PyYAML ... description: YAML parser and emitter for Python ... homepage: https://github.com/yaml/pyyaml ... keywords: [YAML, serialization, configuration, persistence, pickle] ... """) {'keywords': ['YAML', 'serialization', 'configuration', 'persistence', 'pickle'], 'homepage': 'https://github.com/yaml/pyyaml', 'description': 'YAML parser and emitter for Python', 'name': 'PyYAML'} >>> print(yaml.dump(_)) name: PyYAML homepage: https://github.com/yaml/pyyaml description: YAML parser and emitter for Python keywords: [YAML, serialization, configuration, persistence, pickle] ``` Maintainers =========== The following people are currently responsible for maintaining PyYAML: * Ingy döt Net * Matt Davis and many thanks to all who have contributed! See: https://github.com/yaml/pyyaml/pulls Copyright ========= Copyright (c) 2017-2021 Ingy döt Net <in...@in...> Copyright (c) 2006-2016 Kirill Simonov <xi...@re...> The PyYAML module was written by Kirill Simonov <xi...@re...>. It is currently maintained by the YAML and Python communities. PyYAML is released under the MIT license. See the file LICENSE for more details. |