[Info-vax] OpenVMS Development Annoyances

[Arne Vajhøj]

On 4/8/2019 11:09 AM, Stephen Hoffman wrote:
> Another and longer-term consideration here is around what will probably 
> be an eventual migration toward what .NET and such provide; toward OO 
> interfaces into the system and the libraries.  The compatibility with 
> the "new" calling standard that'll eventually be arising here.  Those 
> changes are obviously not going to happen anytime soon, but remaining 
> compatible with the solutions for C++ would be preferable, as the rest 
> of the OpenVMS APIs are made more compatible with OO environments, 
> including with the eventual OOBASIC implementation and support that'll 
> keep David entertained.

I agree that long term such a new OO SYS API is needed.

C++ support is obvious.

Pascal and Basic could probably be extended to support the
necessary OO features (other have done so).

Fortran, Cobol and C I don't see go there.

But that API would not contain descriptors so I don't see
any compatibility issue with just picking something for
descriptors in current API.

Arne