[Info-vax] Error Messages in Basic - %BASIC-E-PARMODNOT, mode for parameter <n> of routine <procedure-name> not as declared

Arne Vajhøj arne at vajhoej.dk
Sun Jun 9 15:54:33 EDT 2019


On 6/9/2019 3:33 PM, Dave Froble wrote:
> On 6/9/2019 2:48 PM, Neil Rieck wrote:
>> If VSI is smart (and I think they are) they will not change a thing
>> with VMS-BASIC. I doubt many organizations are still using this
>> language but for those that are, the programmers already know how to
>> get around most of the warts. On top of that, compiler changes
>> sometimes make it difficult to compile old code (without renovation)
>> so new or changed features would need to be enabled with an option
>> statement or command line parameter.
> 
> Well, after reading a statement from Clair some time back, something to 
> the effect of "we will always offer BASIC on VMS", I'm going to doubt 
> you are correct with your "doubt".  Perhaps he knows a bit more than you 
> do?
> 
> While the desire may exist, I have never heard anyone talking about 64 
> bit BASIC.  That might be one of the biggest changes VSI could consider. 
>   Maybe no demand?
> 
> Can there be enhancements?  Anything can be enhanced.  Sometimes with 
> great benefits.
> 
> As for "warts", got a list.  I got a short list.  But then again, in any 
> language, who doesn't?  Warts should be addressed.

If VMS is to become a commercial success then VSI needs
new applications to be written for VMS.

The majority of those will probably be written
in non-native languages. For VMS that could mean:
Java, Kotlin, Scala, Groovy, PHP, Python etc..

But some may want to use a native language
even for a business application.

C++ is probably the most likely candidate for that.

But given language characteristics then Pascal and Basic
could be argued to be better suited for the purpose.

At least if they get a 25 year upgrade.

Arne







More information about the Info-vax mailing list