Re: New egg: libyaml
Mario Domenech Goulart via Chicken-users <[email protected]> Mon, 29 Dec 2025 19:50:47 +0100
| Newsgroups | gmane.lisp.scheme.chicken |
|---|---|
| Message-ID | <[email protected]> |
Hi, On Sun, 28 Dec 2025 21:18:58 +0000 li lu via Chicken-users <[email protected]> wrote: > I'd like to add a new egg `libyaml` to online packages, > the release-info URI is: > - https://codeberg.org/rikuri/libyaml.ss/releases/download/latest/libyaml.ss.release-info > > The egg is to parse yaml. > About the existing egg `yaml`, > there are issues about distinguish list, mapping, NULL, etc. > So I specifically defined the yaml object in scheme: > - https://codeberg.org/rikuri/libyaml.ss/src/branch/main/docs/usage.md#yaml-and-scheme > > and libyaml is based on it. Would it be possible to have the issues you mention addressed in the existing yaml egg? It's a bit odd to have two eggs to parse YAML, both based on the same C library. We have a similar situation with JSON eggs, which confuses new users (as in "which JSON egg should I use?"). Please don't take this comment as a criticism, but as a feedback: I find the interface and the coding style of the libyaml egg very unidiomatic. I might have not been able to fully grasp its interface, but the coding style is definitely very different from what Schemers normally use (granted, there are small variations when it comes to style, but generally people tend to loosely folow [0]). I only bring this up because it might hinder contributions and/or understanding of the code. [0] https://mumble.net/~campbell/scheme/style.txt All the best. Mario -- https://parenteses.org/mario