Many of my users write math-oriented scripts. Do you have any opposition to a binary operator that computes power?

I was thinking that ** wouldn't cause any conflicts since AngelScript doesn't support * for pointer dereferencing.

I think that might work, yes.

Are you planning to implement this support?

I was going to either implement it in the compiler or as a pre-processing feature, depending on whether you would accept it in the compiler (I didn't want to maintain a fork).

The C-runtime "pow" function always returns a floating-point number. Do we want this behavior even if the operator is used between two integers (i.e. 3 ** 4 ==> 81.0 )?

Something like this might also be used for vector cross products.

Of course, this operator would be able to be overloaded like any of the other math operators.

Regarding my earlier post, I am inclined to make ** not always return a double. I am inclined to think it should behave like the other math operators and return the same type as the operands when possible. I will look into an integer implementation that is better than a simple multiply loop.

If the power-of operator is implemented as a built-in operator it should keep the type of the operands (with appropriate implicit casts when they are not equal). Much like how it is done for other math operators.

And yes, it should be possible to overload it as well for, e.g. by registering/implementing the opPow/opPow_r methods.

You'll need to implement new bytecode instructions for this too. Internally in the bytecode instructions can possibly use the pow() function and then convert the result to the correct type. This is of course if you don't find a more efficient way of calculating power-of. :)

I think I will implement my own integer power function. I've done some limited testing and found that it is up to ten times faster to do the calculation with integers than to pass integers through the floating-point pow() function.

Where should I put the powi and powi64 functions? Should I create a new file in the project?

Also, it is fairly easy for powi to overflow. Should I detect overflows and set an exception? Overflow detection is pretty cheap. I can pre-calculate a table with 64 entries and assign the maximum value of a base for any given exponent. For my users I think it would be helpful to see an overflow exception.

You can just add the powi and powi64 functions to one of the existing modules, e.g. as_context.cpp where I assume they will be most frequently called. Once I merge the code into the SVN I'll consider creating separate file for these utility functions or not.

Try to keep the way the operators work the same regardless on the type they're working on. I agree that having an overflow exception can be useful (similar to the division by zero exception), but the float and double versions should also throw the same exception.

Here's my attempt at a ** and **= operator. I've tested it with VS 2013 and MinGW GCC 4.8.1.

Let me know if you have any questions.

Thanks a lot. I'll review the patch and merge it into the trunk as soon as I can.