unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: bug-guile@gnu.org
Subject: Re: Weird scm_to_latin1_string() behavior.
Date: Sat, 10 Sep 2011 11:39:15 -0700	[thread overview]
Message-ID: <87vct0s0mk.fsf@pobox.com> (raw)
In-Reply-To: <877h5hji54.fsf@localhorst.mine.nu> (David Hansen's message of "Sat, 10 Sep 2011 03:33:27 +0200")

On Fri 09 Sep 2011 18:33, David Hansen <david.hansen@gmx.net> writes:

> the attached code produces
>
> $ ./a.out
> foo,bar
> bar
>
> while I would expect
>
> $ ./a.out
> foo
> bar

I applied Stefan's fix.  Thanks for the report, and thanks to Stefan for
the patch.

Andy
-- 
http://wingolog.org/



      parent reply	other threads:[~2011-09-10 18:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10  1:33 Weird scm_to_latin1_string() behavior David Hansen
2011-09-10 14:03 ` Stefan Israelsson Tampe
2011-09-10 18:39 ` 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=87vct0s0mk.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.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).