Opened 15 years ago
Closed 15 years ago
#303 closed feature_request (fixed)
Access numerical precison / real kind from SINDARIN
| Reported by: | ohl | Owned by: | kilian |
|---|---|---|---|
| Priority: | P3 | Milestone: | v2.0.2 |
| Component: | core | Version: | 2.0.0 |
| Severity: | major | Keywords: | |
| Cc: |
Description
Tests that fail in double precision can pass with higher precision. It should be possible to adapt the tests according to the numerical precision, i.e. the default real kind. It'trivial to implement, but what would be an intuitive interface?
- EPSILON()
- PRECISION(), RANGE()
- #bits
- #bytes
- "single" / "double" / "quadruple"
A funny example is helicity.sin, which fails at quadruple precision, because it is too precise ...
Change History (2)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Implemented the intrinsic variables real_range (int), real_precision (int), real_epsilon (real), real_tiny (real) in r2372. Closing.
Note: See
TracTickets for help on using
tickets.
What about a predefined, locked string variable "$precision" with is either "single" / "double" / "quadruple"? Easy to implement and easy to check.