From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Mark H Weaver <mhw@netris.org>
Cc: Guile Devel <guile-devel@gnu.org>
Subject: Re: Including sjson (formerly (ice-9 json)) and fash.scm in guile proper?
Date: Sat, 13 May 2017 20:30:55 -0500 [thread overview]
Message-ID: <871srs9qcw.fsf@dustycloud.org> (raw)
In-Reply-To: <87lgq1hoou.fsf@netris.org>
Mark H Weaver writes:
> Hi Chris,
>
> Christopher Allan Webber <cwebber@dustycloud.org> writes:
>> So a while ago, David Thompson submitted (ice-9 json) to Guile proper.
>> A few changes were requested, so it hadn't made it in. In the meanwhile
>> I began using it for a number of projects. I also added some
>> modifications and extensions: #nil became 'null for the representation
>> of null values,
>
> Most of the modifications you've made are good, but I'm very
> uncomfortable with the use of #nil in this API. #nil is a terrible hack
> which may not even be adequate for its intended use case. Its existence
> in any data structure is likely to cause misbehavior in other Scheme
> code that is exposed to it, because it violates a longstanding fact in
> Scheme that there is only one value that is treated as "false". It
> would also make it difficult or impossible to port this library, and
> thus anything that depends on this library, to other Scheme systems. We
> should not promote its use by incorporating it into new APIs.
>
> What do you think?
Oh! No you got it backwards, the library *was* using #nil initially,
and I modified it to use 'null now instead. :)
So I think you'd be probably pretty happy!
> Otherwise, I'm generally in favor of incorporating this library into
> Guile, after we make sure that it is robust against malicious inputs.
Okay, cool! The other thing is to add more specific error messages, as
discussed.
What examples of malicious inputs should we test against?
next prev parent reply other threads:[~2017-05-14 1:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 23:17 Including sjson (formerly (ice-9 json)) and fash.scm in guile proper? Christopher Allan Webber
2017-05-12 19:15 ` Mark H Weaver
2017-05-14 1:30 ` Christopher Allan Webber [this message]
2017-05-15 18:35 ` Mark H Weaver
2017-05-15 19:53 ` Christopher Allan Webber
2017-06-20 22:47 ` Mark H Weaver
2017-06-20 23:18 ` Mark H Weaver
2017-06-20 23:50 ` Mark H Weaver
2017-06-22 16:26 ` Christopher Allan Webber
2017-06-03 13:35 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871srs9qcw.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).