[Info-vax] Python on VMS

[Arne Vajhøj]

On 1/16/2019 5:17 PM, Bill Gunshannon wrote:
> On 1/16/19 4:59 PM, Dave Froble wrote:
>> On 1/16/2019 1:17 PM, Phillip Helbig (undress to reply) wrote:
>>> In article <q1nds2$hic$1 at gioia.aioe.org>, =?UTF-8?Q?Arne_Vajh=c3=b8j?=
>>> <arne at vajhoej.dk> writes:
>>>> Would it be fair to say that the problems for the port is
>>>> not fundamental (*nix'isms that simply can't be implemented
>>>> on VMS) but a resource problem (if there were enough VMS
>>>> enthusiasts working on those libraries then they would be
>>>> ported)?
>>>
>>> It's obviously a resource problem because there is a theorem which says
>>> that any Turing machine can implement another.  :-)
>>
>> That could have several meanings.
>>
>> Implement Unix on VMS?  Why not just run Unix?
> 
> Or implement a workable POSIX interface on VMS.

I suspect that POSIX would not be enough.

VMS already got the stuff in older POSIX versions.

I doubt that adding the difference between current VMS
support and full SUSv4/POSIX2008 will solve the problems.

>> I have to ask, if a product is understood, why not just implement it 
>> on VMS, using VMS capabilities?  Might be easier.  But then, it would 
>> not be portable back to whatever.  So what, from a VMS centric 
>> perspective?

> Personally, I agree with you there.  It would likely make keeping
> up to date more work, but I think it would provide better products
> and, in the long run, require less real effort.
> 
> I have been setting up a whole world of systems for some of the
> stuff I want to play with again.  I am utterly amazed (well, more
> dismayed) at what a morass most of the Unixes have become since
> I was doing this on a daily basis.

Linux dist code base typical grows with 20-30% per year.

Over 20 years then ...

Arne