JSON Lines support
Lassi Kortela
(21 Jan 2020 12:05 UTC)
|
||
Re: JSON Lines support
Amirouche Boubekki
(21 Jan 2020 15:00 UTC)
|
||
Re: JSON Lines support
Lassi Kortela
(21 Jan 2020 22:47 UTC)
|
||
Re: JSON Lines support
John Cowan
(21 Jan 2020 22:51 UTC)
|
||
Re: JSON Lines support
Lassi Kortela
(21 Jan 2020 23:07 UTC)
|
||
Re: JSON Lines support
John Cowan
(22 Jan 2020 00:11 UTC)
|
||
Pretty-printing JSON
Lassi Kortela
(22 Jan 2020 00:22 UTC)
|
||
Re: Pretty-printing JSON
John Cowan
(22 Jan 2020 02:28 UTC)
|
||
Different kinds of JSON writers, and naming them
Lassi Kortela
(22 Jan 2020 11:52 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
John Cowan
(22 Jan 2020 18:37 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
Lassi Kortela
(22 Jan 2020 22:33 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
John Cowan
(22 Jan 2020 22:44 UTC)
|
||
Re: Different kinds of JSON writers, and naming them
Duy Nguyen
(23 Jan 2020 10:01 UTC)
|
||
Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 15:30 UTC)
|
||
Re: Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 15:35 UTC)
|
||
Re: Optional features in SRFIs
Arthur A. Gleckler
(24 Jan 2020 15:57 UTC)
|
||
Re: Optional features in SRFIs
John Cowan
(24 Jan 2020 17:01 UTC)
|
||
Re: Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 17:07 UTC)
|
||
(missing)
|
||
Re: Optional features in SRFIs Lassi Kortela (24 Jan 2020 18:43 UTC)
|
||
Re: Optional features in SRFIs
Lassi Kortela
(24 Jan 2020 17:12 UTC)
|
>> The R7RS version of cond-expand supports (library (foo bar)) >> expressions >> to test for a library that can be imported using (import (foo bar)). >> Would it work in principle to put part of the procedures in a SRFI into >> a separate library, or have I misunderstood how (library ...) works? > Yes, a SRFI can document multiple libraries, and can say that all or > only some are required for conformance, and cond-expand can figure out > what libraries are in fact available and perhaps work around any that > are missing. > > What Scheme programs can't currently do is to reflect at the level of > "Does this library provide this procedure/macro, or not?" That limitation is probably a blessing in disguise. It seems like dubious design if a particular library exports a different set of identifiers depending on environmental conditions.