- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Compiler Options and COMP values on Disk
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
01-03-2012 08:55 AM
01-03-2012 08:55 AM
Re: Compiler Options and COMP values on Disk
You're correct, John; I wouldn't expect nor suggest the use of #file or various of the C-ish #pragma directives here.
But as for using language features, that particular suggestion can cut both ways. Porting code to VMS is getting more and more interesting as the years pass. C99 use has become widespread in open source, and code dependent on the newer Fortran standards are increasingly common, too. (I don't port as much COBOL around, but I'd be surprised if that code wasn't also encountering problems.) And these feature deficits are often why I'm conditionalizing the source code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2012 09:06 AM
01-03-2012 09:06 AM
Re: Compiler Options and COMP values on Disk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2012 09:24 AM
01-03-2012 09:24 AM
Re: Compiler Options and COMP values on Disk
>>> I don't see "any #file or #line directives left in the output", and a "#" in column one seems to be pretty Fortran-compatible. If a COBOL compiler is harder to satisfy, then additional options include writing one's own preprocessor, and filtering the output of a sub-ideal preprocessor.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2012 09:44 AM
01-03-2012 09:44 AM
Re: Compiler Options and COMP values on Disk
>I don't see "any #file or #line directives left in the output", and a "#" in column one seems to be pretty Fortran-compatible.
Well these lines:
# 1 "ALP$DKC0:[SMS.ITRC]arch_test_c.for;2"
The "#line" directive is C and C++ Standard. But the preprocessor "# line-number [optional filename]" form is also pretty common.
>simply use gcc which has a -P option:
Right.
- « Previous
- Next »