[asterisk-bugs] [JIRA] Commented: (ASTERISK-18722) ast_expr2 reports "op_times: overflow" on some calculations, though the number is calculated correctly.

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-18722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197924#comment-197924 ] 

Matt Jordan commented on ASTERISK-18722:
----------------------------------------

Please be aware that AEL is an extended support module, and support for it typically comes from the Asterisk community.  As such, response times may reflect that.

> ast_expr2 reports "op_times: overflow" on some calculations, though the number is calculated correctly.
> -------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-18722
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-18722
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration
>    Affects Versions: SVN, 1.6.2.20
>         Environment: CentOS 5.7 32 and 64 Bit
>            Reporter: Ian Anderson
>            Severity: Minor
>
> It seems when Asterisk 1.6.20 (may affect alter versions as the ast_expr2.y code looks same in SVN) does some multiplication (and I believe division) calculations, it will report an overflow error when checking the results.
> Eg. Set(test=$[((0.0046 * 30) / 20) + ((0.0046 * 1) / 10)])
> results in Asterisk returning test=0.00736 (CORRECT) however this is seen in the console
> [Oct 13 17:56:16] WARNING[3153]: ast_expr2.y:1458 op_times: overflow
> It appears that when the chk_times is run (also may affect chk_div),the reversed calcuation doesn't equal (floating point issue?) and thus the warning is generated.  Depending on the numbers in the calculation the error may or may not appear, but when it appears it is always reproducable with the same numbers.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira