MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101
            Thunderbird/24.6.0
Message-ID:  <53A12567.90105@clear.net.nz>
Date:         Wed, 18 Jun 2014 17:36:39 +1200
Reply-To: Mailing list for the LaTeX3 project
              <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
Sender: Mailing list for the LaTeX3 project <LATEX-L@LISTSERV.UNI-HEIDELBERG.DE>
From: aparsloe <aparsloe@CLEAR.NET.NZ>
Subject: Bug in l3fp
To: LATEX-L@LISTSERV.UNI-HEIDELBERG.DE
Precedence: list
Envelope-To: <rainer.schoepf@GMX.NET>
Status: R

\fp_eval:n {  exp(1) - (1+1/1009)^{1009}  } -> 0.001346
\fp_eval:n {  exp(1) - (1+1/1010)^{1010}  } -> 0.001613

\fp_eval:n {  exp(1) - (1+1/1011)^{1011}  } -> 0.001343


(1+1/n)^n should approach e monotonically, so there is clearly an error 
when n = 1010.


Similarly, there are errors when n = 1020 and 1032, and at 505 (half of 
1010, but 510 and 516 seem to be OK).


Andrew


PS. I haven't been testing l3fp integer by integer (truly). This just 
popped out at me when testing a LyX package based on l3fp that I've been 
working on.