Path: utzoo!attcan!uunet!husc6!mailrus!utah-gr!donn
From: donn@utah-gr.UUCP (Donn Seeley)
Newsgroups: comp.unix.wizards
Subject: Re: BSD 9.2 [History of BSD Unix]
Summary: in search of a free Pascal compiler
Message-ID: <2805@utah-gr.UUCP>
Date: 24 Aug 88 07:53:34 GMT
References: <16836@adm.ARPA> <274@umbio.MIAMI.EDU> <3763@omepd> <12285@ncoast.UUCP>
Organization: University of Utah CS Dept
Lines: 31

[I'm crushed that no one has remembered the notorious 8.2 BSD...  9.2
BSD was the obvious successor, but was never implemented.]

	From: allbery@ncoast.UUCP (Brandon S. Allbery)

	...
	I have heard that Berkeley is taking the time to divide the BSD
	sources into the part that requires an AT&T license and the
	part that doesn't.  Which side will the Pascal compiler fall on?

Almost certainly, the AT&T side.  It's probably not a problem that Ken
Thompson helped to write it, but it certainly is a problem that it
generates PCC (/lib/f1) intermediate code.  There's also the yacc issue
(see below).  As for the translator/interpreter system, it's possible
that these sources are independent from AT&T; if the yacc problem is
resolved, it might be possible to use the non-compiler part of Pascal.

	...  One of the things he said to me was that it required a
	modified yacc.  Is that so?  ...

Yes, Berkeley Pascal uses its own version of yacc, called 'eyacc'.

I've thought about implementing a PCC intermediate code front end for
GCC.  If Berkeley Pascal turned out to be free, such a back end could buy
you a compiler.  I'm not sure if it's worth it, though.

This is one of the few times I've heard anyone express any desire to use
Berkeley Pascal except as a last resort,

Donn Seeley    University of Utah CS Dept    donn@cs.utah.edu
40 46' 6"N 111 50' 34"W    (801) 581-5668    utah-cs!donn