Hi, On Mon, 29 Dec 2025 21:19:57 +0000 li lu <[email protected]> wrote:
> - About making a complete library by updating the existing yaml egg > > I don't think it is a good ieda. > > In the earlier version of the old egg, > it cannot distinguish yaml-mapping and yaml-list, > and I (partly)fixed it in the source of old egg: > - https://github.com/tenderlove/chicken-yaml/pull/19 > > And later I find more confusing cases in the old egg. > Considering the design of the old egg, > and the specification of YAML, I think it is hard to fix, > and almostly unable to make a correct parser based on the design of old egg. > > Details are a bit complicated, as a summary of limitation of the old egg: > - The old egg can only correctly parse narrow cases of YAML > - Most YAML cases cannot be identified after parsing > > The next item would show the limitation more specifically. > > - About which one should be used > > As mentioned, the old egg can only parse narrow cases of YAML, > here are some cases that would break the data, > or make the parser generate ill format: > - If there is emplty yaml-list or yaml-mapping > - If there is a yaml-list contain yaml-mapping, or reverse > - If there are multiple yaml-document > - ... > > If there is any nested structure, > the old egg may make error data, > while the new egg should work fine. Alright. Thanks for the clarification. I was not aware of the issues of the yaml egg. I've added libyaml to C5. All the best. Mario -- https://parenteses.org/mario
