SRFI 233: INI files Arthur A. Gleckler (10 Aug 2022 19:20 UTC)
Re: SRFI 233: INI files Vladimir Nikishkin (11 Aug 2022 04:36 UTC)
Re: SRFI 233: INI files Vladimir Nikishkin (11 Aug 2022 04:46 UTC)
Re: SRFI 233: INI files Arthur A. Gleckler (11 Aug 2022 06:08 UTC)
Re: SRFI 233: INI files Marc Nieper-Wißkirchen (11 Aug 2022 14:18 UTC)
Re: SRFI 233: INI files Lassi Kortela (11 Aug 2022 07:53 UTC)
Re: SRFI 233: INI files Vladimir Nikishkin (11 Aug 2022 08:40 UTC)
Re: SRFI 233: INI files Lassi Kortela (11 Aug 2022 08:50 UTC)
Re: SRFI 233: INI files John Cowan (11 Aug 2022 14:01 UTC)
Re: SRFI 233: INI files Hugo Hörnquist (12 Aug 2022 09:50 UTC)
Re: SRFI 233: INI files John Cowan (12 Aug 2022 23:33 UTC)

Re: SRFI 233: INI files Lassi Kortela 11 Aug 2022 08:50 UTC

> Again, I am no expert, so I can only state my opinion that (it is one
> of those extremely rare cases that) having neither would be better
> than having both.
> (Since each user would have to implement such simple code from scratch
> if needed, and thus bear full responsibility for the
> incompatibilities, which will be unavoidable either way.)

+1