Path: utzoo!dptcdc!jarvis.csri.toronto.edu!mailrus!wasatch!cs.utexas.edu!uunet!yale!leichter
From: leichter@CS.YALE.EDU (Jerry Leichter (LEICHTER-JERRY@CS.YALE.EDU))
Newsgroups: comp.arch
Subject: Re: Complex Instructions
Message-ID: <57320@yale-celray.yale.UUCP>
Date: 17 Apr 89 16:12:43 GMT
Sender: root@yale.UUCP
Organization: Yale Computer Science Department, New Haven, Connecticut, USA
Lines: 22
X-from: leichter@CS.YALE.EDU (Jerry Leichter (LEICHTER-JERRY@CS.YALE.EDU))

In article <17296@cup.portal.com>, bcase@cup.portal.com (Brian bcase Case) writes...
>>
>>Try calling Pascal from PL/I under MVS sometime.
> 
>I don't want this to get out of hand, and it might belong elsewhere anyway.
> 
>BUT, was calling Pascal from PL/I under MVS a design goal?  If so, then why
>doesn't the existence of the VAX's CALLS instruction guarantee this goal
>will be met?  I guess this is yet another point:  if the CALLS instruction
>was included so that inter-language calls "would just work," then it fails
>even at that!

Ahem.  Last time I checked, MVS didn't run on VAXes; it ran on IBM mainframes.

VMS runs on VAXes.  It was a design goal of VMS that Pascal code be callable
from PL/I code.  It is.  (Yes, there are complications when you cross over
into an area where both languages specify "how the world should look" - for
example, the I/O system.)

I have no idea what goals MVS may have had in this are.

							-- Jerry