unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: Guile User Mailing List <guile-user@gnu.org>
Subject: Re: fix for c99dev string escape char read
Date: Wed, 22 Nov 2017 19:28:16 -0800	[thread overview]
Message-ID: <0CA89721-C620-4156-B1AD-479132B2D98F@gmail.com> (raw)
In-Reply-To: <87o9nthhg3.fsf_-_@gnu.org>


> On Nov 22, 2017, at 6:11 PM, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
> 
> Hi Matt,
> 
> Working with guile-2.0.14 (soon 2.0.9) on your recent c99dev branch I
> need attached patch.
> 
> So, guile-2.0 resurrected, yay!

But there will be issues with 2.0in general  since, IIRC, SRFI-43 is in guile-2.0.13 but not guile-2.0.11,
or something to that order.  I don't know how far you want to go with the backward compatability.






  reply	other threads:[~2017-11-23  3:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-11 17:19 [ANN] nyacc 0.82.2 is released Matt Wette
2017-11-11 18:37 ` [ANN] nyacc 0.82.3 " Matt Wette
2017-11-11 19:53   ` Jan Nieuwenhuizen
2017-11-11 19:59     ` Jan Nieuwenhuizen
2017-11-11 20:00     ` Matt Wette
2017-11-11 22:03   ` [ANN] nyacc 0.82.4 " Matt Wette
2017-11-23  2:11     ` fix for c99dev string escape char read Jan Nieuwenhuizen
2017-11-23  3:28       ` Matt Wette [this message]
2017-11-23  5:43         ` Jan Nieuwenhuizen
2017-11-23  7:02           ` Jan Nieuwenhuizen
2017-11-23 14:45             ` Matt Wette
2017-11-23 15:04               ` Matt Wette
2017-11-23 15:14                 ` Jan Nieuwenhuizen

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=0CA89721-C620-4156-B1AD-479132B2D98F@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=janneke@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).