Previous versions use to automatically evaluate strings as numbers. In the new
version, strings are not automatically evaluated as integers.

For example, previous versions set "result" as TRUE:

var myNumber = "7";
if(myNumber > "5"){
result = TRUE;
} else {
result = FALSE;
}

The new player sets "result" as FALSE.

Older flash plugins would automatically evaluate the strings "7" and "5" as
numbers. However the new flash player does not.

So... it seems like the new flash player version 10 is more strict with regard
to type casting?

The example is based on an SWF that is output as Flash version 8, actionscript
version 2.

What player (exact version) are you using, as in target build and the player
you ran it in?

I just did a few of tests using your code, building the swf in CS3 and the
last in Flex 3 Compiler:

Target player Flash 8 with AS2 running in Flash Player 9.0.124.0,
Target player Flash 8 with AS2 running in Flash Player 10.0.12.10 Beta,
Target player Flash 9 with AS3 running in Flash Player 9.0.124.0,
Target player Flash 9 with AS3 running in Flash Player 10.0.12.10 Beta,
Flex 3 Compiler target Flash 10 Beta running in Flash Player 10.0.12.10 Beta
(my current environment),

All of which did return the correct result. As in true. (TRUE however gives
undefined in some cases, so I just changed your caps TRUE/FALSE to lower case
true/false, but thats not the issue you're having).

I don't have FP 10.0.12.36 yet as I'm just shocked that final is released
already. And just look at the versions, last beta was 10.0.12.10 and the final
is 10.0.12.36... so if versioning is [ major . minor . revision . 4th number ]
(I'm not really sure what the 4th number means... some kind of build maybe,
which is the part that shocks me... only 26 'builds' later and the beta became
a final? Not even a revision version change? Ouch!)

Also, Flash Players (including FP 10.0.12.10 Beta, and the final FP 10.0.12.36
probably) don't evaluate strings as numbers. Strings are actually evaluated as
text using the alphabetical order. Here's a line from the Flash CS3 IDE Help
File: "String expressions are evaluated using alphabetical order; all capital
letters come before lowercase letters." So in your example, I was getting
'true' because the character '7' comes after the character '5', not because the
strings were converted to numbers. Here's some code that demonstrates why thats
important to keep in mind...

The following code returns true:

var myNumber:String = "seven";
var result:Boolean;
if( myNumber > "five" ){
result = true;
} else {
result = false;
}
trace(result);
// trace will print: true

However, the following code will return false:

var myNumber:String = "SEVEN";
var result:Boolean;
if( myNumber > "five" ){
result = true;
} else {
result = false;
}
trace(result);
// trace will print: false

As you can see (I'm assuming your environment does the same), you might assume
that 'SEVEN' will be evaluated as greater than 'five', but its not, because
capital letters come before lower case letters. So it's important to test
strings in the same case (both capital or lower) unless you have reason to use
the strings as the are and know what to expect from the results.

I'm not sure what exact player you're using, but I couldn't reproduce your
results in any of my test cases.

The issue is not the evaluation of the word "five" or "seven" -- but rather the
evaluation of the number "5" or "7" when the number is wrapped in quotes. When
a number is wrapped in quotes, it is now being interpreted as a "string" and
not an integer number.

Older versions of the plugin would automatically convert the integers that
were wrapped with "quotes" into true integers. The new version of the plugin no
longer auotmatically converts integers that are wrapped in quotes (e.g.
strings) as if they were integer numbers.

The example with "five" and "seven" was to show you that the '<' and '>'
operators when used with strings, work by comparing the string characters using
alphabetical order. Previous version of flash worked the same. "5" and "7" were
not converted to integers, but were rather compared as strings. Since "5" is
before "7" in alphabetical order, you would get the result that 5 is less than
7. The new player works the same, and I ran your example code and it works just
fine. You must have a different issue in your code that is causing your issue.
Look in the flash help file under operators to see how it works. It clearly
states that numbers as strings get interpreted as strings... by checking each
char in the alphabetical order and hence "5" is less then "7". The are not
converted to true integers and never were.

The issue is not the evaluation of the word "five" or "seven" -- but rather the
evaluation of the number "5" or "7" when the number is wrapped in quotes. When
a number is wrapped in quotes, it is now being interpreted as a "string" and
not an integer number.

Older versions of the plugin would automatically convert the integers that
were wrapped with "quotes" into true integers. The new version of the plugin no
longer auotmatically converts integers that are wrapped in quotes (e.g.
strings) as if they were integer numbers.

The example with "five" and "seven" was to show you that the '<' and '>'
operators when used with strings, work by comparing the string characters using
alphabetical order. Previous version of flash worked the same. "5" and "7" were
not converted to integers, but were rather compared as strings. Since "5" is
before "7" in alphabetical order, you would get the result that 5 is less than
7. The new player works the same, and I ran your example code and it works just
fine. You must have a different issue in your code that is causing your issue.
Look in the flash help file under operators to see how it works. It clearly
states that numbers as strings get interpreted as strings... by checking each
char in the alphabetical order and hence "5" is less then "7". The are not
converted to true integers and never were.

The issue is not the evaluation of the word "five" or "seven" -- but rather the
evaluation of the number "5" or "7" when the number is wrapped in quotes. When
a number is wrapped in quotes, it is now being interpreted as a "string" and
not an integer number.

Older versions of the plugin would automatically convert the integers that
were wrapped with "quotes" into true integers. The new version of the plugin no
longer auotmatically converts integers that are wrapped in quotes (e.g.
strings) as if they were integer numbers.

The example with "five" and "seven" was to show you that the '<' and '>'
operators when used with strings, work by comparing the string characters using
alphabetical order. Previous version of flash worked the same. "5" and "7" were
not converted to integers, but were rather compared as strings. Since "5" is
before "7" in alphabetical order, you would get the result that 5 is less than
7. The new player works the same, and I ran your example code and it works just
fine. You must have a different issue in your code that is causing your issue.
Look in the flash help file under operators to see how it works. It clearly
states that numbers as strings get interpreted as strings... by checking each
char in the alphabetical order and hence "5" is less then "7". The are not
converted to true integers and never were.