From: Andy Wingo <wingo@igalia.com>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: 26013-done@debbugs.gnu.org, ludo@gnu.org
Subject: bug#26013: (srfi srfi-37) chokes on empty string parameter
Date: Thu, 20 Apr 2017 10:59:47 +0200 [thread overview]
Message-ID: <cucr30no3ng.fsf@igalia.com> (raw)
In-Reply-To: <20170419.183229.1069589305335594566.post@thomasdanckaert.be> (Thomas Danckaert's message of "Wed, 19 Apr 2017 18:32:29 +0200 (CEST)")
On Wed 19 Apr 2017 18:32, Thomas Danckaert <post@thomasdanckaert.be> writes:
>> On Tue 07 Mar 2017 16:34, Thomas Danckaert <post@thomasdanckaert.be>
>> writes:
>>
>>> It looks like Guile's srfi-37 implementation doesn't process empty
>>> string arguments correctly.
> I don't fully understand the code in srfi-37.scm, but I think the fix
> can be as simple as the attached patch (i.e. first check if the argument
> is empty, otherwise check if it starts with \#-).
Applied, thanks :)
Andy
prev parent reply other threads:[~2017-04-20 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 15:34 bug#26013: (srfi srfi-37) chokes on empty string parameter Thomas Danckaert
2017-04-19 15:13 ` Andy Wingo
2017-04-19 16:32 ` Thomas Danckaert
2017-04-20 8:59 ` Andy Wingo [this message]
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=cucr30no3ng.fsf@igalia.com \
--to=wingo@igalia.com \
--cc=26013-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=post@thomasdanckaert.be \
/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).