From: arne@vajhoej.dk
On 12/8/2025 9:12 AM, Simon Clubley wrote:
> On 2025-12-05, Arne Vajhøj wrote:
>> So what is missing for programming? I would say biggest
>> items are:
>> * loops
>> * switch/case
>> * arrays
>> * user defined lexicals
>
> New functionality is implemented as a OO model in C, which sits alongside
> the existing procedural code in Macro-32.
>
> Lists/dictionaries/tuples/etc should be a core facility.
>
> General OO functionality with structured imports of the objects.
>
> Generation of the VMS header files for all the languages will also
> include generation of DCL OO headers and modules that can be directly
> imported by a DCL script.
>
> As such, there is no need for user defined lexicals (which, with the
> current DCL design, would have to run in user mode instead of supervisor
> mode anyway for security reasons). You just import the OO module containing
> the system service that you want to call.
????
Having a script language call native code requires some builtin
capability in the script language.
Examples: Python ctypes, VBScript COM etc..
>> This mean VSI cannot break backwards compatibility for DCL - whatever
>> ran in 1985 has to run the exact same way today.
>
> No problem. You keep the existing interfaces and add OO functionality
> on top of it for use by new scripts, or any existing scripts you might
> want to spend the time modifying. There's no reason why all the new OO
> stuff can't simply be written in C that runs alongside the existing
> Macro-32 code. Likewise for all the new control structures stuff.
????
You need one parser not two parsers.
You need some interoperability between new stuff and old stuff.
Arne
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
