From: Wilfred Hughes <me@wilfred.me.uk>
To: Julian Graham <joolean@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [PATCH] Fix tree-il code generation for ECMAscript `new' expression.
Date: Tue, 20 Sep 2016 21:55:53 -0400 [thread overview]
Message-ID: <CAFXAjY4QBzh50OgjKh98Z+KdeSq3BpNyvzPLkKD=YfgftXOd4g@mail.gmail.com> (raw)
In-Reply-To: <CANdC_RBjj4meqDSzeniKWne9JYmppVJtvU4pvmB5cqcfzo9Yug@mail.gmail.com>
Excellent :)
I'm afraid I can't help you further, but it's great to see the
ecmascript frontend get some attention. The lack of ASI is the bug
that I notice the most, but there's definitely low hanging fruit.
Wilfred
On 20 September 2016 at 10:26, Julian Graham <joolean@gmail.com> wrote:
> Hi Wilfred,
>
> Yep! The FSF should have my assignment on file.
>
>
>
> On Tue, Sep 20, 2016 at 12:32 AM, Wilfred Hughes <me@wilfred.me.uk> wrote:
>> Looks good to me (even tests)! Have you assigned copyright papers for Guile?
>>
>> On 13 September 2016 at 08:42, Julian Graham <joolean@gmail.com> wrote:
>>> Hi Guilers,
>>>
>>> Noticed that ECMAscript "new" syntax seemed to be broken. Here's a
>>> patch that fixes it. I'd like to make some incremental improvements in
>>> Guile's ECMAscript support, so if this one's welcome, expect others to
>>> follow!
>>>
>>>
>>> Regards,
>>> Julian
next prev parent reply other threads:[~2016-09-21 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 12:42 [PATCH] Fix tree-il code generation for ECMAscript `new' expression Julian Graham
2016-09-20 4:32 ` Wilfred Hughes
2016-09-20 14:26 ` Julian Graham
2016-09-21 1:55 ` Wilfred Hughes [this message]
2016-09-25 2:38 ` Julian Graham
2016-10-25 21:41 ` 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='CAFXAjY4QBzh50OgjKh98Z+KdeSq3BpNyvzPLkKD=YfgftXOd4g@mail.gmail.com' \
--to=me@wilfred.me.uk \
--cc=guile-devel@gnu.org \
--cc=joolean@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).