[Info-vax] General Availability of 9.2 for x86-64

VAXman- at SendSpamHere.ORG VAXman- at SendSpamHere.ORG
Fri Jul 15 21:12:21 EDT 2022


In article <62d1d488$0$701$14726298 at news.sunsite.dk>, =?UTF-8?Q?Arne_Vajh=c3=b8j?= <arne at vajhoej.dk> writes:
>On 7/15/2022 4:12 PM, Bill Gunshannon wrote:
>> On 7/15/22 15:05, Arne Vajhøj wrote:
>>> On 7/15/2022 10:35 AM, Bill Gunshannon wrote:
>>>> On 7/15/22 09:08, Arne Vajhøj wrote:
>>>>> On 7/15/2022 9:02 AM, Simon Clubley wrote:
>>>>>> On 2022-07-14, Arne Vajhøj <arne at vajhoej.dk> wrote:
>>>>>>> https://vmssoftware.com/about/roadmap/ says:
>>>>>>>
>>>>>>> July
>>>>>>> OpenVMS V9.2 (Limited Production Release)
>>>>>>> ...
>>>>>>> Native compilers with LLVM backend code generator:
>>>>>>>       BLISS, XMACRO, C++ (Phase 1)
>>>>>>> ...
>>>>>>> July-November
>>>>>>> ...
>>>>>>> Additional native compilers
>>>>>>>       C, COBOL, and C++ (Phase 2 ? VMS Extensions)
>>>>>>
>>>>>> Interesting that COBOL is a way higher priority than Fortran.
>>>>>
>>>>> I think that was to be expected.
>>>>
>>>> Wonder where all of these VMS COBOL users are.
>>>
>>> You do see COBOL questions here occasionally.
>> 
>> Can't remember the last time I saw one.
>
>Google finds 3 question the last 12 months:
>
>Brian June 10th
>Jan-Erik September 20th
>Jan-Erik August 14th
>
>(I will not insult Brian by calling him a Cobol user,
>but there must be some Cobol usage involved)

Puhleez, COBOL is barely a read-only language.  I was only trying to
find how to put a LINK time symbol into what any normal person would 
call a *byte- sized* variable but a COBOler would call PIC COMP 9(9)
X(21) XYZZY(WUZNOT) SOMTHING.OR.OTHER. whatever they call a variable
in COBOL so I could tell a customer how to properly invoke $CREPRC.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

I speak to machines with the voice of humanity.



More information about the Info-vax mailing list