[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Fix tree-il code generation for ECMAscript `new' expression.
|
From: |
Wilfred Hughes |
|
Subject: |
Re: [PATCH] Fix tree-il code generation for ECMAscript `new' expression. |
|
Date: |
Tue, 20 Sep 2016 21:55:53 -0400 |
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 <address@hidden> wrote:
> Hi Wilfred,
>
> Yep! The FSF should have my assignment on file.
>
>
>
> On Tue, Sep 20, 2016 at 12:32 AM, Wilfred Hughes <address@hidden> wrote:
>> Looks good to me (even tests)! Have you assigned copyright papers for Guile?
>>
>> On 13 September 2016 at 08:42, Julian Graham <address@hidden> 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