You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 1817 Reporter: administrator Status: acknowledged Resolution: open Priority: normal Severity: feature Category: standard library Tags: patch Related to:#4748 Monitored by:@Chris00
Bug description
Full_Name: william margolis
Version: 3.06
OS: linux (suse 8.1)
Submission from: adsl-63-199-206-139.dsl.lsan03.pacbell.net (63.199.206.139)
I understand why this is occuring, according to the standard sequencing through
the complex division algorithm. But, for people working on the Rieman sphere,
it would be very, very pleasant if 1/0 could register as, say {Complex.re = infinity; Complex.im = 0.} or something similar !?
This would certainly please extended-complex-plane people. (We expect a/0 = an
infinity type, not an nan...)
In any case, my desire is that I may be able to distinguish in the complex case
between nan and infinity cases, without having to create, say:
type sphere = INF | C of float * float ;;
and do all the argument matching comparisons each time.
It seems that the better one can do is to follow the ISO/IEC 9899:1999 standard, annex G (IEC 60559-compatible complex arithmetic (informative), pages 465–478. ANSI, 1999.). Then
which is an infinity because a complex number with any infinite component is considered infinite (the only complex NaN is { re = nan; im = nan }. I have uploaded the file "complex_test.ml" with an implementation of mul and div.
See also: ftp://ftp.win.ua.ac.be/pub/preprints/03/criticism.pdf
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
This issue has been open one year with no activity. Consequently, it is being marked with the "stale" label. What this means is that the issue will be automatically closed in 30 days unless more comments are added or the "stale" label is removed. Comments that provide new information on the issue are especially welcome: is it still reproducible? did it appear in other contexts? how critical is it? etc.
Original bug ID: 1817
Reporter: administrator
Status: acknowledged
Resolution: open
Priority: normal
Severity: feature
Category: standard library
Tags: patch
Related to: #4748
Monitored by: @Chris00
Bug description
Full_Name: william margolis
Version: 3.06
OS: linux (suse 8.1)
Submission from: adsl-63-199-206-139.dsl.lsan03.pacbell.net (63.199.206.139)
I love the Complex module, BUT:
I understand why this is occuring, according to the standard sequencing through
the complex division algorithm. But, for people working on the Rieman sphere,
it would be very, very pleasant if 1/0 could register as, say
{Complex.re = infinity; Complex.im = 0.}
or something similar !?This would certainly please extended-complex-plane people. (We expect a/0 = an
infinity type, not an nan...)
In any case, my desire is that I may be able to distinguish in the complex case
between nan and infinity cases, without having to create, say:
and do all the argument matching comparisons each time.
Is there an easy/efficient implementation !?
File attachments
The text was updated successfully, but these errors were encountered: