Rhino compatibility with angular 1.3.8

[stefanofornari]

I am opening another issue regarding Rhino compatibility with angular 1.3.8. The good news is that I managed to get it to work, at least so far, but there are a few tweaks to make. I hope they can be applied to the code base because they are quite basic.

I am attaching two files:

1. angular-1.3.8.diff[1] contains a few changes to angular.js make it digestible by Rhino
2. ecma5-adapter.js[2] contains a few functions that I had to create to support some ECMA5 features not available in Rhino.

I am sorry if I can not produce a PR, but I am new to JS development environments and I am not familiar with the build. If a PR is mandatory and you are OK in merging the changes I am proposing I will be happy to take the load to make the PR.

[1] https://drive.google.com/file/d/0BzWVgSXXLzyTbVVyeWdTSjNHWjA/view?usp=sharing
[2] https://drive.google.com/file/d/0BzWVgSXXLzyTWGU3c01jRWZzb00/view?usp=sharing

[realityking]

According to http://kangax.github.io/compat-table/es5/ a current version of Rhino should support String.prototype.trim and Array.isArray.

However I don't think it's a good idea to prominent support of Rhino in AngularJS. Development seems to have all but stopped, and support for a 5 year old standard doesn't seems unreasonable.

[stefanofornari]

I would agree if there were major changes. given they are minor I would consider it. in particular not using int as function name. I would also argue about the argument of how old is a technology to decide to support it, although I would agree that if no one else but me is interested in supporting Rhino, not taking it into account makes sense.
thanks for you quick reply :)

[lgalfaso]

The change to add the functions that are part of ES5, that will not happen. The part on renaming int, that is very reasonable, it is a duplicate of #7768, but it should happen in a future release