07:09 <d_bot> <sarna> hey I'm trying to parse some ini files. I found `ocaml-inifiles` on opam, but where's the source/documentation for it?

07:09 <d_bot> <sarna> all the links I found were dead ends

08:35 <d_bot> <sarna> found the source - from 2004, LGPL, uses classes

08:43 <Armael> ye I've also wondered before why there's no good library for ini files

08:43 <d_bot> <andreypopp> probably some toml parser could be adapted to parse ini?

08:43 <d_bot> <andreypopp> "loose mode" toml

09:21 <d_bot> <sarna> Armael: especially when it should be fairly easy to write when you know stuff like menhir (I don't)

09:22 <d_bot> <sarna> wouldn't it be easier to just write an ini parser?

09:22 <d_bot> <sarna> ini compatibility was explicitly rejected https://github.com/toml-lang/toml/issues/411

09:31 <d_bot> <andreypopp> maybe, I'm not a fan of either but my understanding was that TOML is a "specified INI" with extra complexity on top

11:17 <d_bot> <sarna> I liked TOML until I tried actually using it haha

11:17 <d_bot> <sarna> do you have a preference? I'm curious

11:23 <d_bot> <andreypopp> For user-specified config files?

11:23 <d_bot> <andreypopp>

11:23 <d_bot> <andreypopp> Something with jsonschema support (editors can provide diagnostics and completion based on it) — json with relaxed syntax (comments, allowed, trailing commas), strict subset of YAML.

11:33 <d_bot> <sarna> ah, but then editor support is meh

11:34 <d_bot> <sarna> (I mean when you use json with relaxed syntax)

11:44 <d_bot> <sarna> unless I'm missing something?

11:54 <d_bot> <andreypopp> I think vscode is fine with that (and this is probably the only popular editor which supports jsonschema validation out of the box)... so it depends on what audience you are targeting... yaml is also fine I think (especially if you stay with some strict subset)

13:04 <companion_cube> @andreypopp you mean json5

13:06 <d_bot> <andreypopp> @companion_cube I think there are multiple "dialects" of that thing, I think vscode calls it jsonc (json with comments)

13:08 <companion_cube> vscode does its own thing as always

13:08 <companion_cube> https://json5.org/

13:08 <companion_cube> at least that one is a bit more fleshed out imho

13:33 <d_bot> <Christophe> oh god yes trailing comma

13:34 <companion_cube> yes please

15:58 <dmbaturin> companion_cube: Out of curiosity, what's good about trailing commas? I'm not against them, I just wonder what use cases are made easier.

16:07 <companion_cube> dmbaturin: editing the godamn file :D

16:07 <companion_cube> just put a comma after each field

16:07 <companion_cube> so you can delete/add them easily

16:07 <companion_cube> or shuffle them

16:07 <companion_cube> same with OCaml btw.

17:07 <d_bot> <leviroth> It also makes for nicer diffs