<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>Yes in terms of ratio that is a huge improvement :) , but having functions that fail when a number reach a certain size is a ticking bomb, for instance if you use them for timetagging. <div><br></div><div>I agree also that the 2^62+256+1 is not directly a bug, but it may not be obvious everyone that a sum of integers shall be calulated via float aritmetics. </div><div><br></div><div>Jan Å</div> <br><br><br><div style="font-size:100%;text-align:left;color:#000000">-------- Original message --------<br>From: Samuel Gougeon <<br></div><blockquote cite="mid:321bf67f-b693-cede-d03d-a99a8213eefb@online.no" type="cite">
</blockquote>
Yes, but this loss is expected, since 2^62+256+1 is performed with
decimal encoding.<br>
It is a case similar to the classical 1+ %eps/2<br>
It is not a bug.<br>
For dec2*(): int64 encoding is already supported, and a clear error
message is yielded for input integers > 2^52<br>
<br>
<tt>--> dec2bin(int64(2^52))</tt><tt><br>
</tt><tt> ans =</tt><tt><br>
</tt><tt> 10000000000000000000000000000000000000000000000000000</tt><tt><br>
</tt><tt><br>
</tt><tt>--> dec2bin(int64(2^53))</tt><tt><br>
</tt><tt>at line 12 of function dec2bin (
SCI\modules\elementary_functions\macros\dec2bin.sci line 43 )</tt><tt><br>
</tt><tt>dec2base: Wrong value for input argument #1: Must be
between 0 and 2^52.</tt><tt><br>
</tt><br>
So, there is still a limitation, but it is clearly stated. At least,
integers from 2^33 to 2^52 are newly supported :)<br>
<br>
Samuel<div><br></div><div><br dir="auto">
<br dir="auto">
</div></body></html>