Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

The qualifiers, and most (all?

Qualifiers
0
Posted

The qualifiers, and most (all?

0

pragmas, that may be of interest when migrating VAX C code to HP C include: o Failure to specify the prefixing qualifier (on certain and usually older versions of C) can cause the compiler to not add the prefixes for the names of the C library routines into the references placed in the object module, which can in turn cause problems resolving the external symbols in the library when the object code is linked: /PREFIX=ALL_ENTRIES o Some VAX C programs erroneously write to the string literals. By default, HP C does not allow the constants to change. /ASSUME=WRITABLE_STRING_LITERALS o Enables sharing (“shr”) of globals and of extern variables. HP C sets externs as non-shareable (“noshr”), VAX C as “shr”. /SHARE_GLOBALS 10-19 OpenVMS Programming Information o VAX C assumes common block model for external linkages. /EXTERN_MODE=COMMON_BLOCK o Refers to the padding placed between member elements within a struct. Disabling member alignment packs the data more tightly into memory, but this pac

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.