Performance & overload again...

Dave,

with some efforts I came down to only :) a 50% loss in interpreted mode w=
ith=20
overloaded operators abilited! However the loss is only significative in=20
nested loops and similar structures that require a lot of iterations.=20
In "normal" page programming the user experiences no loss of performance.

On the other side, in compiled mode, the loss is 0% and programs execute =
at=20
the same speed even during very complex loops, with or without overloaded=
=20
operatos abilited.

I'm confident that some work can be done to make the interpreted mode fas=
ter=20
even in complex loops with operator overloading abilited, but I think tha=
t a=20
certain delay (needed to check the function hashtable for a suitable oper=
ator=20
function) cannot be avoided.

So what to do? I think that we should keep the feature, work to make it m=
ore=20
performant and accept a certain delay, only in interpreted mode and only =
in=20
special situations.=20

What do you think?

Stefano