[Info-vax] OpenVMS Development Annoyances

[Dave Froble]

On 4/6/2019 10:07 PM, Stephen Hoffman wrote:
> On 2019-02-08 16:08:30 +0000, Stephen Hoffman said:
>
>> Things about developing for OpenVMS that have annoyed me (again) this
>> month:
>> ...

So, use Basic ...

> C++ has little OpenVMS system integration.  Outside of OpenVMS message
> files, there seems little else.   Nothing obvious in iostream, for that
> matter.

Use Basic

> Specifying RMS file attributes on the fopen() is entertaining when
> working with the strict compilation mode, as the compilations produce
> (expected) diagnostics for the OpenVMS fopen extensions.

Use Basic

> Which meant reverting and switching to __USE_STD_IOSTREAMS to get the
> C++98-era "modern" behavior.

Use Basic

> C does slightly here with OpenVMS, but still lacks OpenVMS integration.

Use Basic

> OpenVMS descriptors, RMS, etc., most of what could be useful for working
> with C++ on OpenVMS is seemingly missing.

Use Basic

> Keeping old code mostly-working is certainly valuable, but the
> "Specifying /DEFINE=__USE_STD_IOSTREAM forces the inclusion of the ANSI
> standard version of the iostream header file.
>
> This is the default in STRICT_ANSI mode. Otherwise, the pre-standard
> AT&T-compatible version of iostream is used." is a stinky default for
> anything other than remedial work.

Ah, I enjoyed that ....

:-)

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486