nukim@uunet.uu.net (kyongsok kim) (10/17/89)
PPC (path pascal compiler) developed at UIUC (Univ. if Illinois at Urbana-Champaign) is supposed to run on the Vax and Sun. When I tried to compile a sample program after installing ppc on a Sun/4, ppc was looking for "/lib/f1" which does not exist on Sun/4's (there is one on the vax though.) If anybody has installed ppc successfully on a Sun/3 or 4, please let me know. I have another question. If anybody ported ppc to Solbourne successfully, please let me know. Thanks in advance. Kyongsok Kim Dept. of Comp. Sci., North Dakota State University e-mail: nukim@plains.nodak.edu; nukim@ndsuvax.bitnet; uunet!ndsuvax!nukim
grunwald@ncar.ucar.edu (10/19/89)
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)