guile-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

guile-json, SRIFs and licenses


From: Zelphir Kaltstahl
Subject: guile-json, SRIFs and licenses
Date: Wed, 6 Nov 2019 09:19:01 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

Hi!

What is the requirement in terms of licenses for SRFI implementations?

I personally think that MIT is a terrible license (one of the I don't
care licenses) as it does not make sure, that modifications flow back to
the community. Do SRFIs require MIT license? And if so, why?

~ Zelphir

On 11/6/19 1:28 AM, John Cowan wrote:
> +1.  If only it weren't GPL3, which makes it ineligible to be a SRFI
> implementation....
>
> Is there any chance of dual-licensing it under MIT?
>
> On Tue, Nov 5, 2019 at 7:03 PM Zelphir Kaltstahl <address@hidden>
> wrote:
>
>> This is great! A solid JSON parsing and outputting library is important
>> for a programming language these days! Thanks for your work!
>>
>> On 11/5/19 6:00 PM, address@hidden wrote:
>>> Message: 1
>>> Date: Mon, 4 Nov 2019 22:28:12 -0800
>>> From: Aleix Conchillo FlaquƩ <address@hidden>
>>> To: guile-user <address@hidden>
>>> Subject: [ANN] guile-json 3.3.0 released
>>> Message-ID:
>>>       <
>> address@hidden>
>>> Content-Type: text/plain; charset="UTF-8"
>>>
>>> Hi,
>>>
>>> I'm pleased to announce guile-json 3.3.0. This new version comes with a
>> few
>>> improvements: guile-json will now throw an exception if the native scheme
>>> value used to build a JSON document is invalid (this is done before
>>> printing any JSON). Also, an additional key argument #:validate can be
>>> given to ignore the validation in the case performance is important and
>> the
>>> data is known to be valid. Empty JSON array slots are also considered
>>> invalid, before they were generating an invalid scheme representation. A
>>> few more details can be found on the NEWS file.
>>>
>>> https://github.com/aconchillo/guile-json
>>>
>>> Best,
>>>
>>> Aleix
>>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]