-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rounding glitch from bigint to float #63
Comments
I don't know what it means.
…On Wed, 19 Oct 2022, 23:37 Jean-Luc-Picard-2021, ***@***.***> wrote:
Hi,
Did some regression testing:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Trealla Prolog 2.4.3
% ?- trealla.
% case, trealla: 0
% case2, trealla: 0
% case3, trealla: 0
% case4, trealla: 0
% case5, trealla: 0
% case6, trealla: 0
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Trealla Prolog 2.4.23
% ?- trealla.
% case, trealla: 0
% case2, trealla: 0
% case3, trealla: 0
% case4, trealla: 0
% case5, trealla: 0
% case6, trealla: 16
Is this to expect? Test cases here:
Compliance Dogelog Spieler novacore/arithmetic
http://pages.xlog.ch/littab/doclet/docs/10_samples/04_doge_comply/novacore/arithmetic/package.jsp
Maybe this was done in favor of performance?
—
Reply to this email directly, view it on GitHub
<#63>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFNKSEXXV446RPD36ZKVG53WD72TJANCNFSM6AAAAAARJEJY4M>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Ok |
My bad, was using wrong test cases. But when I use
The five failing test cases are among the same problems For example this Trealla Prolog result is a litle too low
of a similar routine used by Trealla Prolog as in Ciao Prolog, |
Pushed a change to devel branch, if you could try it.
…On Fri, Oct 21, 2022 at 10:44 AM Jean-Luc-Picard-2021 < ***@***.***> wrote:
My bad, was using wrong test cases. But when I use
the most recent ones, I get these results:
case3, trealla: 5
case4, trealla: 0
case5, trealla: 0
case6, trealla: 0
The five failing test cases are among the same problems
as here for Cioa Prolog:
ciao-lang/ciao#77 <ciao-lang/ciao#77>
—
Reply to this email directly, view it on GitHub
<#63 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFNKSEVEJHWQYJ6QSIHWGYTWEHRPRANCNFSM6AAAAAARJEJY4M>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Hi, I have streamline the test suite a little bit.
You should get the test cases and a lot of other stuff, via the following,
And then updates of the test cases.
But I hope I am now finished with updating them, except |
As of now I have float/1 conversion in the test case:
Do you say I can remove it now? And query:
I am testing the other Prolog systems without float/1. This would be another ticket here: |
Ok, float/1 can be removed. |
I don't know what the status of this is. |
The new version of Trealla Prolog returns another value:
But since this is an extremly nasty test case, the rounding least significant bit, of the given bigint as well.
Hence the result is not yet correct. One can compare:
So cannot yet close this ticket. |
Scryer Prolog has the same bug:
|
Hi,
Did some regression testing:
Is this to be expected? Test cases here:
Compliance Dogelog Spieler novacore/arithmetic
http://pages.xlog.ch/littab/doclet/docs/10_samples/04_doge_comply/novacore/arithmetic/package.jsp
Maybe this was done in favor of some performance?
The text was updated successfully, but these errors were encountered: