[Info-vax] VMS Software needs to port VAX DIBOL to OpenVMS X86 platform

[1tim....@gmail.com]

On Tuesday, December 22, 2020 at 8:02:15 AM UTC-7, Bill Gunshannon wrote:
> On 12/21/20 11:16 PM, Dave Froble wrote: 
> > On 12/21/2020 9:07 PM, Arne Vajhøj wrote: 
> >> On 12/21/2020 3:15 PM, 1tim.... at gmail.com wrote: 
> >>> On Saturday, December 19, 2020 at 6:35:01 PM UTC-7, Arne Vajhøj wrote: 
> >>>> On 12/19/2020 5:44 PM, 1tim.... at gmail.com wrote: 
> >>>>> here is a more modern Dibol example - not 99 bottles of beer. it was 
> >>>>> written just to test a String parser class, written in Dibol. 
> >>>>> 
> >>>>> import parser 
> >>>>> import System.Collections 
> >>>>> 
> >>>>> record 
> >>>>> 
> >>>>> parse , at StringParser 
> >>>>> arry , at ArrayList 
> >>>>> proc 
> >>>>> parse = new StringParser() ;; create instance of parser 
> >>>> Again the code is for .NET platform (System.Collections.ArrayList). 
> >>>> 
> >>>> If all modern Dibol code is being written for .NET (.NET is a great 
> >>>> platform so I can understand that) then that may explain why 
> >>>> Dibol on VMS x86-64 is still TBD. 
> >>> 
> >>> wrong, that is OpenVMS Code. And Linux Code. That is Modern DBL 
> >> 
> >> 
> >> You got System.Collections.ArrayList on VMS?? 
> >> 
> >> Arne 
> > 
> > I got no idea what that is, but, why not? I'm assuming that it is some 
> > procedure, and such can be implemented in almost any language. Doesn't 
> > mean there is not a lot of code behind the capability, just that the 
> > user doesn't have to write that code. A bit like what everyone seems to 
> > like about things such as Python. 
> >
> Like with COBOL and a number of other legacy languages my objection 
> is when they totally change the language and still have the nerve to 
> call it what it was. Like calling "DELPHI" "Pascal" or calling "ANSI 
> C" "C". If you want a new language then give it a new name and stop 
> pretending it's something it is not. Kinda like calling "Windows" 
> "VMS" because Cutler helped develop it. 
> 
> bill

Ironically, you'd be more correct to call windows Prism than VMS - with a very healthy dose of OS/2 thrown in.