HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- using fortran and profor with upgraded VMS and Ora...
Operating System - OpenVMS
1828492
Members
2647
Online
109978
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2010 01:14 AM
07-30-2010 01:14 AM
Re: using fortran and profor with upgraded VMS and Oracle
ignore that last question mike got that now with
real*16 max_real_16
parameter (max_real_16 = huge(0.0_16))
real*16 max_real_16
parameter (max_real_16 = huge(0.0_16))
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2010 04:09 AM
07-31-2010 04:09 AM
Re: using fortran and profor with upgraded VMS and Oracle
>John: No matter how much floating point precision you have, you WILL get calculation errors
Not if you are using decimal floating point. :-)
Not if you are using decimal floating point. :-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2010 01:25 PM
08-01-2010 01:25 PM
Re: using fortran and profor with upgraded VMS and Oracle
re: Dennis,
>decimal floating point
True, but I'm specificically talking about BINARY FPFPR, which is all you get in Fortran and C.
In languages that support a Binary Coded Decimal (BCD) data types, like COBOL and BASIC, you can safely use them for monetary calculations, but in (for example) Fortran, C and Pascal where floating point is finite precision binary, it's very important that programmers understand the limitations of FPFPR arithmetic. Just one example, I'd contend that when using these data types, any code comparing two FPFPR variables for equality (".EQ." or "==") is almost certainly incorrect.
I'm concerned that the reason Robert is using (very) high precision data types (REAL*16) in this example is an attempt to "fix" the kind of errors which are inherent in the data type. It's fine for calculating load values on bridges, or astronomical distances, but NOT for calculating cap values for stocks or bank balances!
>decimal floating point
True, but I'm specificically talking about BINARY FPFPR, which is all you get in Fortran and C.
In languages that support a Binary Coded Decimal (BCD) data types, like COBOL and BASIC, you can safely use them for monetary calculations, but in (for example) Fortran, C and Pascal where floating point is finite precision binary, it's very important that programmers understand the limitations of FPFPR arithmetic. Just one example, I'd contend that when using these data types, any code comparing two FPFPR variables for equality (".EQ." or "==") is almost certainly incorrect.
I'm concerned that the reason Robert is using (very) high precision data types (REAL*16) in this example is an attempt to "fix" the kind of errors which are inherent in the data type. It's fine for calculating load values on bridges, or astronomical distances, but NOT for calculating cap values for stocks or bank balances!
A crucible of informative mistakes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2010 08:51 PM
08-01-2010 08:51 PM
Re: using fortran and profor with upgraded VMS and Oracle
>John: which is all you get in Fortran and C.
>but in (for example) Fortran, C and Pascal where floating point is finite precision binary
The next C Standard supports Decimal Floating Point and this is implemented on HP-UX 11.31.
>it's very important that programmers understand the limitations of FPFPR arithmetic.
Exactly, I learned that many decades ago.
>but NOT for calculating cap values for stocks or bank balances!
That's why DecFP was added to C.
>but in (for example) Fortran, C and Pascal where floating point is finite precision binary
The next C Standard supports Decimal Floating Point and this is implemented on HP-UX 11.31.
>it's very important that programmers understand the limitations of FPFPR arithmetic.
Exactly, I learned that many decades ago.
>but NOT for calculating cap values for stocks or bank balances!
That's why DecFP was added to C.
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP