straighten out int() -> toInt() conversion in the preproc

also additional float casting problems, i.e:

float u = float(x)/width; works.
float u = (float(x)/width); doesn't work: "unexpected token: float".
float u = (x/float(width)); works!

return (int(5.5)) causes an error
http://processing.org/discourse/yabb/YaBB.cgi?board=Proce55ing_software_bugs;action=display;num=1083624993;start=0

more reports of sadness:
http://processing.org/discourse/yabb_beta/YaBB.cgi?board=Syntax;action=display;
num=1116887165;start=0#3

float(i*oneCycle*freq)
where i and freq are int and freq is float, it says: perhaps you wanted the overload version
"float toFloat(boolean $1);" instead?

and with the int conversion:
int(i*oneCycle*freq)
doesn't give any problem.

http://processing.org/discourse/yabb/YaBB.cgi?board=Proce55ing_software_bugs;action=display;num=1084011098

perhaps related...

in 0091 Beta (windowsxp)...

String test = "5.0";
int testi = int( test );
println( test + " -> " + testi ); //5.0 -> 0

(In reply to comment #4)
> perhaps related...
>
> in 0091 Beta (windowsxp)...
>
> String test = "5.0";
> int testi = int( test );
> println( test + " -> " + testi ); //5.0 -> 0

nope, that's your own bug.. you can't parse a float as an int. you have to parse it as a float
and then cast it as an int. though i guess that makes for a weird setup because the parsing
and the casting are the same.. hrmmm..

*** Bug 397 has been marked as a duplicate of this bug. ***

Possibly related n 0135 Beta (Mac OS X):

int yframe = 500;
int xframe = 500;
float frameLength = 6.0;
float frameCenter = 0.0;

float evalMaxx = frameCenter + ( frameLength * ( float(xframe) / float(yframe) ) );

yields "unexpected token: float"

likely related:

int yframe = 500;
int xframe = 500;
float frameLength = 6.0;
float frameCenter = 0.0;

float evalMaxx = frameCenter + ( frameLength * ( float(xframe) / float(yframe) ) );

yields "unexpected token: float"

yup, though this all hinges on bug #598, which is basically that the
grammar needs to be completely redone.

I seem to have accidentally killed this bug when I stabbed #598. Fixed?

yep, these ones are at least confirmed to work. great!