Pull up tamings___ to global namespace.

JS runtime compilation is not happy when variable "tamings___" is declared multiple times, one in each feature.

[Jasvir, 2011-02-18 22:08:26]

LGTM

Should other features all depend on global?

[mhermanto, 2011-02-19 02:23:38]

Update patch

[mhermanto, 2011-02-19 02:26:11]

It turns out that we'd need more tamings/caja globals declared. To avoid
polluting namespace for all features (depending on globals), I've created
feature=taming, and have only tamed features (ie: features with taming.js)
depend on it. This is more verbose, but more focussed. PTAL.

On Fri, Feb 18, 2011 at 6:23 PM, <mhermanto@gmail.com> wrote:

> Update patch
>
>
> http://codereview.appspot.com/4187052/
>

[johnfargo, 2011-02-23 00:34:55]

LGTM

The downside of putting tamings into its own feature is that the <dependency>
ends up in quite a few more places. But it is more descriptive, so seems ok..

On 2011/02/19 02:26:11, mhermanto wrote:
> It turns out that we'd need more tamings/caja globals declared. To avoid
> polluting namespace for all features (depending on globals), I've created
> feature=taming, and have only tamed features (ie: features with taming.js)
> depend on it. This is more verbose, but more focussed. PTAL.
> 
> On Fri, Feb 18, 2011 at 6:23 PM, <mailto:mhermanto@gmail.com> wrote:
> 
> > Update patch
> >
> >
> > http://codereview.appspot.com/4187052/
> >