[Info-vax] VSI Community License Program - x86

[bill]

On 4/10/2023 4:16 PM, Arne Vajhøj wrote:
> On 4/10/2023 10:19 AM, bill wrote:
>> On 4/9/2023 8:05 PM, Arne Vajhøj wrote:
>>> On 4/9/2023 11:35 AM, bill wrote:
>>>> On 4/9/2023 11:27 AM, Craig A. Berry wrote:
>>>>> On 4/9/23 9:56 AM, bill wrote:
>>>>>> I haven't downloaded it yet but I hope to get to it this week.
>>>>>> I will probably try VirtualBox on Windows10.
>>>>>> Can anyone tell me what compilers come with it as that is what I
>>>>>> would be most interested in trying out.
>>>>>
>>>>> Looks like there are field test versions of C (traditional front end
>>>>> with LLVM translator), C++ (based on clang++), and FORTRAN.  IIRC 
>>>>> COBOL
>>>>> is supposed to be next with BASIC "hopefully this year."
>>>>
>>>> Well, that's a small bummer.  My biggest interest is in COBOL but I
>>>> guess I could play with the Fortran a bit.  But my interest in 
>>>> Fortran runs out around Fortran-77.  :-)
>>>
>>> It should compile Fortran 77 just fine.
>>
>> I thought VMS Fortran was up at least to Fortran 99.  I was just
>> hinting that, like COBOL, I have no interest in and see little
>> value in the more modern accretions.
> 
> Fortran 90/95.
> 
> So they added a ton of features. But they did not remove
> the old stuff.
> 
> So your Fortran 77 code should compile fine.
> 
> (I believe the Fortran 90 standard explicit required Fortran
> 77 compatibility, but that the Fortran 95 standard removed some
> of the 77 stuff, which does not matter as VSI Fortran kept
> that stuff)

As I understand it Fortran (much like COBOL) added a  lot of junk
that had nothing to with the intended function of the language.
In the case of COBOL, thankfully, it was mostly ignored by true
practitioners of the art.  Fortran did not fare as well.

bill