From: Mark H Weaver <mhw@netris.org>
To: Massimiliano Gubinelli <m.gubinelli@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: TeXmacs on Guile 2.2.4
Date: Wed, 29 May 2019 15:29:57 -0400 [thread overview]
Message-ID: <877ea9qcrz.fsf@netris.org> (raw)
In-Reply-To: <049592E2-CAAC-4F43-98F0-FF11E91E792B@gmail.com> (Massimiliano Gubinelli's message of "Mon, 27 May 2019 14:18:21 +0200")
Massimiliano Gubinelli <m.gubinelli@gmail.com> writes:
> While trying some alternative solutions I noticed the following: the
> function scm_to_latin1_stringn calls out to scm_to_stringn with an
> argument NULL for the encoding:
>
> result = scm_to_stringn (str, lenp, NULL,
> SCM_FAILED_CONVERSION_ERROR);
>
> this causes an error in scm_to_stringn since it contains the check:
>
> (c_strcasecmp (encoding, "UTF-8") == 0)
>
> and c_strcasecmp does not check for null pointers. Is this a bug?
Yes, it is. I'll fix it soon, thanks.
Mark
prev parent reply other threads:[~2019-05-29 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-26 21:17 TeXmacs on Guile 2.2.4 Massimiliano Gubinelli
2019-05-26 23:49 ` Mike Gran
2019-05-27 12:18 ` Massimiliano Gubinelli
2019-05-29 19:29 ` Mark H Weaver [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=877ea9qcrz.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-user@gnu.org \
--cc=m.gubinelli@gmail.com \
/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).