Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rice!sun-spots-request
From: boulder!foobar!grunwald@ncar.ucar.edu
Newsgroups: comp.sys.sun
Subject: Re: looking for PATH PASCAL running on SUN or SOLBOURNE
Keywords: Software
Message-ID: <2418@brazos.Rice.edu>
Date: 19 Oct 89 15:37:41 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 27
Approved: Sun-Spots@rice.edu
X-Sun-Spots-Digest: Volume 8, Issue 175, message 6 of 17

Hi, I wrote the version of ppc that was derived from the berkeley pascal
compiler.

Ppc depends on the Berkeley Pascal, which uses a commen code generator.
In 4.3BSD, this code generator was shared by f77 & pc; that's what /lib/f1
is.

In addition to this, there are internal changes to the source for ppc that
would need to be made for a different architecture. I don't remember where
all the stuff is, but if you look for symbols like m68k and/or vax, you'll
probably find the #ifdefs that are needed.

You'll also have to change the runtime library & the context switching
routines. All of this is non-trivial. It would probably take about 2 weeks
or a month if you have /lib/f1 working.

Unless you really need path pascal, another alternative is to use an
extensible language like C++ with a tasking library. I had planned on
writing a PathExpression class, but haven't had the time yet. It's fairly
simple to translate the path notation into P & V's.

Someone at UIUC did this using a pre-processor for C++ -- His extensions
generated code for each class member function mentioned in the path, just
like Path Pascal.  You might contact roy@cs.uiuc.edu (Roy Campbell) to see
who did this work & if it's still available.

Dirk Grunwald -- Univ. of Colorado at Boulder	(grunwald@foobar.colorado.edu)