Eval and unresolved variables in chapter 7 tests.

In chapter 7, there are tests that use eval  to introduce variables into the scope. In Strict mode, eval cannot introduce variables, so is necessary to set up the variables out of the eval. 

There are also some unresolved variablesin the tests, unresolved variables lead to an error in Strict Mode.

[pedro.delgallego, 2010-07-16 12:33:39]

section 7.3

[pedro.delgallego, 2010-07-16 12:35:03]

Section 7.5

[pedro.delgallego, 2010-07-16 12:35:35]

Section 7.6

[pedro.delgallego, 2010-07-16 12:36:15]

section 7.87

[pedro.delgallego, 2010-07-16 12:36:32]

Section 7.8

[christian.plesner.hansen, 2010-08-08 02:38:00]

How have you tested this?

> S7.6_A1.2_T3.js:
> if ( eval($ + '!==' + \u0024)  ) {

What is this meant to test?  Is the $ supposed to be enclosed in quotes?

> S7.6_A1.3_T3.js
> if ( eval(_ + '!==' + \u005F)  ) {

Ditto

[christian.plesner.hansen, 2010-08-08 02:39:49]

Also, remember to publish+mail when uploading a CL or making changes, otherwise
your reviewers won't notice.  I didn't receive an email for some of these CLs,
including this one.