Re: [PATCH] ECMAscript: Bind type names to constructor functions in the global env.

2017-01-16 Thread Julian Graham
On Mon, Jan 9, 2017 at 4:20 PM, Andy Wingo wrote: > I am happy to include patches like this one. > > Yet -- *program-wrappers*, what is that about? I don't even remember > any more. I guess it's for setting a property on a function instance, > even if the function is a normal Guile function? I

Re: [PATCH] ECMAscript: Bind type names to constructor functions in the global env.

2017-01-09 Thread Andy Wingo
On Sat 19 Nov 2016 16:44, Julian Graham writes: > Andy, I'd particularly like your feedback on this approach, as it > relies in part on the use of `*program-wrappers*' (in `(language > ecmascript function)') and I'm not 100% sure I understand the intent > behind that table. I am happy to include

Re: [PATCH] ECMAscript: Bind type names to constructor functions in the global env.

2017-01-08 Thread Julian Graham
Hey Andy, If you're looking at patches, would you look this over and merge it if you like it? Doesn't have to go into 2.1.6 per se, but it would be cool to have it on master. On Sat, Nov 19, 2016 at 10:44 AM, Julian Graham wrote: > Howdy! > > Find attached a patch that makes it so that the foll

[PATCH] ECMAscript: Bind type names to constructor functions in the global env.

2016-11-19 Thread Julian Graham
cc942aec5e Mon Sep 17 00:00:00 2001 From: Julian Graham Date: Sat, 19 Nov 2016 10:28:50 -0500 Subject: [PATCH] ECMAscript: Bind type names to constructor functions in the global env. Per ECMA-262: "The Object constructor is ... the initial value of the Object property of the global o