Wrap proxy.js in a function.

Wrap proxy.js in a function.

Committed: https://crrev.com/7667d19eecd44299f366c987462b6e23e2c217e3
Cr-Commit-Position: refs/heads/master@{#27746}

[Yang, 2015-04-10 10:57:13]

yangguo@chromium.org changed reviewers:
+ mvstanton@chromium.org

[rossberg, 2015-04-10 11:00:27]

rossberg@chromium.org changed reviewers:
+ rossberg@chromium.org

[rossberg, 2015-04-10 11:00:28]

Yay for using the module pattern, just one comment.

https://codereview.chromium.org/1075773003/diff/20001/src/proxy.js
File src/proxy.js (right):

https://codereview.chromium.org/1075773003/diff/20001/src/proxy.js#newcode15
src/proxy.js:15: "use strict";
DBC: is there a reason not to leave this at the top of the file?

[Yang, 2015-04-10 11:05:11]

https://codereview.chromium.org/1075773003/diff/20001/src/proxy.js
File src/proxy.js (right):

https://codereview.chromium.org/1075773003/diff/20001/src/proxy.js#newcode15
src/proxy.js:15: "use strict";
On 2015/04/10 11:00:28, rossberg wrote:
> DBC: is there a reason not to leave this at the top of the file?

I'm considering the option of concatenating all (non-optional) native js files
into one js file (so that references across files don't have to be properties on
the jsbuiltins object anymore). Since some are strict and others are not, having
the strict mode within the function scope would preserve that. Now of course
proxy.js is optional (behind a flag), but I'd like to make this consistent.

[mvstanton, 2015-04-10 11:45:35]

lgtm

[Yang, 2015-04-10 12:02:33]

The CQ bit was checked by yangguo@chromium.org

[commit-bot: I haz the power, 2015-04-10 12:02:51]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1075773003/20001

[commit-bot: I haz the power, 2015-04-10 12:32:24]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-04-10 12:32:37]

Patchset 2 (id:??) landed as
https://crrev.com/7667d19eecd44299f366c987462b6e23e2c217e3
Cr-Commit-Position: refs/heads/master@{#27746}