Issue 4524 in pharo: DomainError signalTo: sets wrong bounds

Status: Accepted
Owner: [hidden email]

New issue 4524 by [hidden email]: DomainError signalTo: sets wrong  
bounds
http://code.google.com/p/pharo/issues/detail?id=4524

Current definition is:
signalTo: end
        ^ self signalFrom: Float infinity to: end

I presume the from bound should be negated

These bounds are not used, but anyway, I'm not sure if they are useful nor  
enough (regarding inclusion of bounds, or unconnected domains like arcotanh)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #1 on issue 4524 by [hidden email]: DomainError signalTo:  
sets wrong bounds
http://code.google.com/p/pharo/issues/detail?id=4524

Yeah, that is a typo, it should be negated.

Indeed, disconnected domains are not covered, I am not sure how that could  
be solved, maybe a small hierarchy ?

The reason for this class is that domain errors are very common and cover  
many error cases


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Updates:
        Status: FixProposed

Comment #2 on issue 4524 by [hidden email]: DomainError signalTo:  
sets wrong bounds
http://code.google.com/p/pharo/issues/detail?id=4524

See inbox SLICE including several changes:
1) fix the lower bound (Float infinity negated)
2) additional API for providing a messageText to the DomainError
3) Use DomainError to handle domain error of functions #ln #log and #arcSin
4) Refactor ln and log for Fraction (simplified formulation)
5) Refactor ln and log for Integer (defined only in LargeInteger, because  
SmallInteger won't overflow)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

Comment #3 on issue 4524 by [hidden email]: DomainError signalTo:  
sets wrong bounds
http://code.google.com/p/pharo/issues/detail?id=4524

Looks OK to me, merci beaucoup, Nicolas.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker